-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
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
Remove client secret field from metatoken #318
Remove client secret field from metatoken #318
Conversation
Reflect the QR code contents: only a URL
``` | ||
POST MyId:MySecret /oauth/token | ||
POST /oauth/token |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't this need to include the client ID as a username, i.e. MyId@/oauth/token
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, I have specified it in the paragraph above this line. I thought it was more clear to explicitly state the use of HTTP basic authentication with client id as username and empty password, then the MyId@
notation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ok, I missed that.
/api/meta-token
responseExceptionTranslator
for Spring Security OAuth'sNoSuchClientException
: trying to initiate an OAuth flow with a non-existing client would result in anInternal Server Error
response, now it is translated to aBad Request
responseCloses #317