Add Client Credentials Flow OIDC authentication #204
Merged
Conversation
This file contains hidden or 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
The authentication is primarily for automated use-cases that use service accounts to log in. Client receives the access token from SSO using its ID and secret. It then sends the access token to the hub, which validates it and logs the user in. The newly added tokenidclogin URL is expected to be protected by mod_oauth2 (or analogous for the used web server), which handles the validation and the passing of REMOTE_USER to Django. XML-RPC client uses the sessionid cookie (which ensures that the user is logged in) provided by Django.
rohanpm
approved these changes
May 30, 2023
emilyzheng
approved these changes
May 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The authentication is primarily for automated use-cases that use service accounts to log in. Client receives the access token from SSO using its ID and secret. It then sends the access token to the hub, which validates it and logs the user in. The newly added tokenidclogin URL is expected to be protected by mod_oauth2 (or analogous for the used web server), which handles the validation and the passing of REMOTE_USER to Django. XML-RPC client uses the sessionid cookie (which ensures that the user is logged in) provided by Django.
Refers to CLOUDDST-18720