-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Support nonce for Authorization Code and Implicit Grant #962
Comments
We aren't supporting OpenId Connect at present but do plan to do so in the future. I don't believe including a nonce is required in any of the RFC's we currently support so don't think this will be added in until full support for OpenId Connect is. |
Hi @m0ark, how did you deal with the missing nonce? |
@m0ark I am interested in this as well. Hit the same issue. |
Any ETA when the official OpenID connect is coming? I am running into the same issue that the |
No plans to add into the next major so likely after that. Steve's repo is the best option for now 👍 |
Sadly it doesn't handle the I can't find any docs of it but seems to be able to solve the issue |
Nvm... V9 isn't even out yet.... |
I added a comment in steverhoades/oauth2-openid-connect-server#47 - how I did it today succesfully |
Currently I have to integrate full OpenId Connect Core spec, so I came across https://github.com/steverhoades/oauth2-openid-connect-server to this library.
OIDC Implicit Flow requires a
nonce
to be included in the id_token issued. (see 3.2.2.1.)In OIDC Authorization Code Grant the request can contain a nonce and in this case it has to be included in the id_token aswell (see 3.1.2.1.).
For OAuth2 handling
nonce
s is only ever mentioned in a security advisory (mentioned in #634), but for OpenId Connect handling is mandatory. Since OpenId Connect is just an extension of OAuth2 i thinknonce
s should be handled by the latter.The text was updated successfully, but these errors were encountered: