Child Item

IOS ASWebAuthenticationSession for OAuth

Previously I used a WKWebView browser control to perform the OAUth. This allowed me to trap the redirect URL to obtain the access code. My redirect URL was http://localhost/Auth

Now I am using the Native browser interface ASWebAuthenticationSession This requires that you use an APPLICATION specific callback URL scheme for your redirect uri. i.e. MyAppName://Auth

The Dropbox APP console allows me to specifiy this as the Redirect URL but gives an error when I try to call the oauth2/authrize endpoint using this as the redirect_uri

Find more posts tagged with

API

Abuse

Accepted answers

RTS S.

Thanks, I used the Code flow as it looked more secure.

It would seem that custom URL schemes would be as secure as LOCALHOST ... both of which can only work on the user's device.

All comments

Greg-DB

Can you share the full URL of the page displaying the error, as well as the text of the error itself? Thanks in advance!

RTS S.

    static let CLIENT_ID = "......"
    static let CLIENT_SECRET = "...."
    static let REDIRECT_URL = "myapp://Auth"
    static let OAUTH_URL = "https://www.dropbox.com/1/oauth2/authorize"

    override func OAuthURL() -> String {
      return String(format:"%@?redirect_uri=%@&amp;response_type=code&client_id=%@&amp;force_reapprove=true",
                    DropboxOAuthInfo.OAUTH_URL,
                    HTTP.urlEncode(DropboxOAuthInfo.REDIRECT_URL),
                    DropboxOAuthInfo.CLIENT_ID)
    }

RTS S.

The image did not get attached ... here it is as a link:

Screen Capture

Greg-DB

Thanks! Based on the code you shared, I see that you're using the "code" flow (i.e., 'response_type=code'). For the code flow, only "https://" is allowed in the redirect URI (unless on localhost), so "myapp://" wouldn't be allowed.

Instead, for client-side applications like this, you should use the "token" flow, i.e., 'response_type=token'. That does allow custom URL schemes in redirect URIs, such as "myapp://".

For more information on how to use the token flow, please refer to the /oauth2/authorize documentation.

RTS S.

Thanks, I used the Code flow as it looked more secure.

It would seem that custom URL schemes would be as secure as LOCALHOST ... both of which can only work on the user's device.

Eddyfc

{"swagger": "2.0", "basePath": "/", "paths": {"/model/metadata": {"get": {"responses": {"200": {"des