-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
fix: Do not include nonce in ID tokens when not used #570
Conversation
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.
Thank you! Can you please address the failing tests?
Fixed tests. |
Are you still up for the changes? :) If you need any help, let us know! |
Converting to draft due to lack of response |
Addressed comments. |
I think CI is failing because of invalid configuration, not because of something I would have introduced in this PR. |
Possible, I restarted the CI! |
Right, we had this issue in another PR. I create a PR in Ory Hydra which bumps the fosite dep to your fork. If the CI passes there, then the one here would also pass! |
It seems it passed. Could this be fixed in CI somehow? It is pretty ugly that (contributing to) this repository now depends in this way on Hydra's one? |
done! |
😎 |
The new version has different behavior for the `nonce` claim, which is now omitted if it would be empty (see ory/fosite#570). Signed-off-by: Matt Moyer <moyerm@vmware.com>
The new version has different behavior for the `nonce` claim, which is now omitted if it would be empty (see ory/fosite#570). Signed-off-by: Matt Moyer <moyerm@vmware.com>
The new version has different behavior for the `nonce` claim, which is now omitted if it would be empty (see ory/fosite#570). Signed-off-by: Matt Moyer <moyerm@vmware.com>
Proposed changes
Not sure why was this there, but it makes no sense and there is no point in making ID tokens larger just to include an empty string.
Checklist
and signed the CLA.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got green light (please contact
security@ory.sh) from the maintainers to push
the changes.
works.
appropriate).