Facing problems getting the Access Token from a user on Windows Form

Gonzo345

Hi there:

 

I actually asked this on StackOverflow but I got no answer yet. The thing is that I'm trying to generate the access token from the user but I can't "capture" the generated token and I'm afraid that asking for permission generates a new access token everytime, so the previous one remains invalid.

 

The point is that my code is not even entering on the try catch part. I'm still guessing what am I doing wrong.

 

private void Start(string appKey, WebBrowser w)
{
    this.oauth2State = Guid.NewGuid().ToString("N");
    //This one finally sha token on the WebClient
    Uri authorizeUri2 = DropboxOAuth2Helper.GetAuthorizeUri(appKey);
    //This one just shown a blank screen (I guess it stucks on the redirect)
    //Uri authorizeUri = DropboxOAuth2Helper.GetAuthorizeUri(OauthResponseType.Token, appKey, redirectUrl, state: oauth2State);
    w.Navigate(authorizeUri2);
}

private void Browser_Navigating(object sender, WebBrowserNavigatingEventArgs e)
{
    if (!e.Url.ToString().StartsWith(redirectUrl, StringComparison.InvariantCultureIgnoreCase))
    {          
        // we need to ignore all navigation that isn't to the redirect uri.
        return;
    }

    try
    {
        OAuth2Response result = DropboxOAuth2Helper.ParseTokenFragment(e.Url);
        if (result.State != this.oauth2State)
        {
            // The state in the response doesn't match the state in the request.
            return;
        }

        this.AccessToken = result.AccessToken;
        this.Result = true;
    }
    catch (ArgumentException)
    {
        // There was an error in the URI passed to ParseTokenFragment
    }
    finally
    {
        e.Cancel = true;
        this.Close();
    }
}

The complete code is on StackOverflow. Sorry for disturbing, but I would really appreciate some help here understanding what's happening. I'm getting too much headaches with this problems related with OAuth2 

 

Thanks in advance,

Gonzo345.

Greg-DB

You can retrieve an access token from the OAuth flow either using or not using a redirect URL, as you saw, but we recommend using a redirect URL when you can, as it streamlines the process.

 

(For reference, if you do copy/paste the code, note that that's an "authorization code" and not an "access token". You need to exchange it for an access token.)

 

Anyway, for the redirect version, it looks like you're seeing the event for the load of the /authorize page itself. That one should be ignored, as you're actually looking for the load after the user clicks to authorize the app, and is sent to the redirect URI. Is that event not firing at all for you?

 

Also, I notice you're using the "Navigating" event. You may want to try the "Navigated" event instead to see if that works better in your case. (We had a blog post about this here, although it wasn't written for use with the newer .NET SDK itself.)