-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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/OIDC loopback redirect dynamic #13871
Feat/OIDC loopback redirect dynamic #13871
Conversation
…IDC client if it is the IPv4 or IPv6 loopback address.
63e4fdc
to
4a66798
Compare
Thanks, @paladin-devops! I had just started working on this issue too :) I'll be giving this a review. |
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.
Thanks again for this contribution, @paladin-devops! I have a few suggestions. I also wrote some tests and am happy to contribute those after this gets merged.
Co-authored-by: Austin Gebauer <[email protected]>
@austingebauer thanks for the feedback & review! My next contribution will include tests up front. :) Looking forward to integrating this w/Waypoint! |
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 again, @paladin-devops. I'll be backporting this into the Vault 1.9.x branch as well.
* Add check for OIDC provider to permit a non-exact redirect URI from OIDC client if it is the IPv4 or IPv6 loopback address. * Update changelog/13871.txt Co-authored-by: Austin Gebauer <[email protected]> * Update redirectURI check to match that for the OIDC auth method. Co-authored-by: Austin Gebauer <[email protected]>
Addresses #13523.
Adds check to OIDC provider to allow for redirect URI to have a dynamic port # in the URI if the loopback address is included in the OIDC client, and if the OIDC client's redirect URI is the loopback address.