DM-41186: Add new route for CADC token metadata #877
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cbanek
approved these changes
Oct 24, 2023
CADC software uses an authentication component designed for use with OpenID Connect that takes a token from the Authorization header and sends it to an endpoint, expecting to get back the validated JWT claims. Since it treats the token as opaque, we can use this with our regular tokens as long as we provide an endpoint that returns user metadata in the expected format. Add /auth/cadc/userinfo as that endpoint, temporarily. Put CADC in the URL because the return format is specific to the current needs of the CADC auth code. In particular, it requires sub to be a UUID (to allow username changes), which we generate based on an optional configuration parameter and the UID of the user using the UUID v5 algorithm.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CADC software uses an authentication component designed for use with OpenID Connect that takes a token from the Authorization header and sends it to an endpoint, expecting to get back the validated JWT claims. Since it treats the token as opaque, we can use this with our regular tokens as long as we provide an endpoint that returns user metadata in the expected format.
Add /auth/cadc/userinfo as that endpoint, temporarily. Put CADC in the URL because the return format is specific to the current needs of the CADC auth code. In particular, it requires sub to be a UUID (to allow username changes), which we generate based on an optional configuration parameter and the UID of the user using the UUID v5 algorithm.