We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
7.3.4. OAuth Flow: Requesting an Access Token Rather than hard coding the token path to /v2/oauth/access_token the token acquisition URL could be another URL made available via the settings URLs. Is it really necessary to redefine the parameters of the token API endpoint? Could this not be deferred to OAuth2?
7.3.4. OAuth Flow: Requesting an Access Token
Rather than hard coding the token path to /v2/oauth/access_token the token acquisition URL could be another URL made available via the settings URLs.
/v2/oauth/access_token
Is it really necessary to redefine the parameters of the token API endpoint? Could this not be deferred to OAuth2?
The point here was to profile OAuth2 to have a narrow always working set of functionality. Likely this needs a second look into.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The point here was to profile OAuth2 to have a narrow always working set of functionality. Likely this needs a second look into.
The text was updated successfully, but these errors were encountered: