-
Notifications
You must be signed in to change notification settings - Fork 372
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
feat: use OIDC ID token for Azure #1269
Conversation
5d4df88
to
608284c
Compare
582d93b
to
c28cbca
Compare
fdeeb99
to
74b58c6
Compare
fed3540
to
e9b120d
Compare
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.
LGTM, thanks for putting this together.
The test secrets might show up under security issues after this is merged so we should probably remember to circle back and mark them.
b13f7d5
to
c337005
Compare
Co-authored-by: Joel Lee <[email protected]>
🎉 This PR is included in version 2.102.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Use the OIDC ID token instead of the UserInfo endpoint, as there are serious discrepancies between what is returned. --------- Co-authored-by: Joel Lee <[email protected]>
@hf -- I've started getting the following error for Azure users logging in:
Is this related to this PR? The errors began at the following timestamp: 2023-10-17T08:59:15.000Z. I am using multitenant sign in. Is the fix here? #1272. |
Use the OIDC ID token instead of the UserInfo endpoint, as there are serious discrepancies between what is returned.