Discogs and Oauth

[ryerman]

@ohrenkino

If you have problems with the discogs page and their way of guiding users to certain functions then try to get help there. It is definitely not an MP3tag problem.

Here is some documentation from Discogs about how an application (like Mp3tag) should ask users to authorize the app on behalf of their Discogs account.

3. Redirect your user to the Discogs Authorize page

Authorization page:

http://discogs.com/oauth/authorize?oauth_t...quest_token>

This page will ask the user to authorize your app on behalf of their Discogs account. If they accept and authorize, they will receive a verifier key to use as verification. This key is used in the next phase of OAuth authentication.

If you added a callback URL to your Discogs application registration, the user will be redirected to that URL, and you can capture their verifier from the response. The verifier will be used to generate the access token in the next step. You can always edit your application settings to include a callback URL (i.e., you don’t need to re-create a new application).

It seems to say that Mp3tag should redirect users to the "Authorization page" (presumably a page like this), before they are asked for an Authorization code.

If the OP is not being re-directed, then there may be a problem with Mp3tag or at least the user's particular installation.

What can users expect to see on screen when first attempting to access Discogs?
Will they be re-directed to an "Authorization page"?

It would be helpful to have a step-by-step guide for users to allow and/or repair access to Discogs, even if some of the steps involve the Discogs website.