View on GitHub
DropboxClientsManager Extension Reference
DropboxClientsManager
Copyright © 2016 Dropbox, Inc. All rights reserved.
-
Starts the OAuth 2 Authorization Code Flow with PKCE.
PKCE allows “authorization code” flow without “client_secret” It enables “native application”, which is ensafe to hardcode client_secret in code, to use “authorization code”. PKCE is more secure than “token” flow. If authorization code is compromised during transmission, it can’t be used to exchange for access token without random generated code_verifier, which is stored inside this SDK.
Note
If auth completes successfully, A short-lived Access Token and a long-lived Refresh Token will be granted. API calls with expired Access Token will fail with AuthError. An expired Access Token must be refreshed in order to continue to access Dropbox APIs.
API clients set up by
DropboxClientsManagerwill get token refresh logic for free. If you need to set upDropboxClient/DropboxTeamClientwithoutDropboxClientsManager, you will have to set up the clients with an appropriateAccessTokenProvider. -
setupWithAppKey(_:transportClient: backgroundTransportClient: secureStorageAccess: includeBackgroundClient: requestsToReconnect: ) -
setupWithAppKey(_:sessionConfiguration: backgroundSessionConfiguration: secureStorageAccess: includeBackgroundClient: requestsToReconnect: ) -
setupWithAppKey(_:backgroundSessionIdentifier: sharedContainerIdentifier: secureStorageAccess: requestsToReconnect: ) -
setupWithAppKeyMultiUser(_:transportClient: backgroundTransportClient: tokenUid: secureStorageAccess: includeBackgroundClient: requestsToReconnect: ) -
setupWithAppKeyMultiUser(_:sessionConfiguration: backgroundSessionConfiguration: tokenUid: secureStorageAccess: includeBackgroundClient: requestsToReconnect: ) -
setupWithAppKeyMultiUser(_:backgroundSessionIdentifier: sharedContainerIdentifier: tokenUid: secureStorageAccess: requestsToReconnect: ) -
-
-
-