-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
sso/oidc: add support for acr_values request parameter #11026
Conversation
🤔 This PR has changes in the |
Co-authored-by: R.B. Boyer <[email protected]>
Co-authored-by: R.B. Boyer <[email protected]>
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
🍒 If backport labels were added before merging, cherry-picking will start automatically. To retroactively trigger a backport after merging, add backport labels and re-run https://circleci.com/gh/hashicorp/consul/448927. |
🍒✅ Cherry pick of commit c4c833f onto |
Co-authored-by: R.B. Boyer <[email protected]>
🍒✅ Cherry pick of commit c4c833f onto |
Co-authored-by: R.B. Boyer <[email protected]>
🍒✅ Cherry pick of commit c4c833f onto |
Co-authored-by: R.B. Boyer <[email protected]>
🍒✅ Cherry pick of commit c4c833f onto |
Co-authored-by: R.B. Boyer <[email protected]>
This is a small change for the OSS side that the enterprise side depends on to make
acr_values
configurable on the OAuth2 authorization request [1]. This particular parameter is one of a few optional parameters that were never supported in our core SSO library because there wasn't a use case when it was originally developed. The successor to our SSO library,hashicorp/cap
does support these and the other optional parameters. We may pursue replacing our SSO library withcap
but until then, we need to add this parameter as a stop-gap for a client request.[1] - OIDC Request Parameters