Technical details about Oauth tokens #15359
-
|
If I understand this correctly oauth tokens (for example for OneDrive) are generated for the requesting client and not for some Cyberduck cloud middleware, right? I think it would really help if you could explain what's happening on a technical level in the background and if iterate has ever access to the authorization code or if it's just the client. Maybe this would be a good place for it: https://docs.cyberduck.io/protocols/onedrive/ How permissions look on onedrive: 
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
There is no middleware or proxy in between. The auth process is just between Mountain Duck and the identity service provider (IdP) of your cloud storage provider. |
Beta Was this translation helpful? Give feedback.
There is no middleware or proxy in between. The auth process is just between Mountain Duck and the identity service provider (IdP) of your cloud storage provider.