HDDS-15273. Add OIDC WebIdentity STS design#10338
Open
paf91 wants to merge 1 commit into
Open
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
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.
What changes were proposed in this pull request?
This PR adds the design document for OIDC/WebIdentity support in Apache Ozone STS.
The design describes how Ozone STS can support an
AssumeRoleWithWebIdentityflow, allowing an OIDC token issued by an external identity provider such as Keycloak to be exchanged for temporary S3credentials.
This is a design-document-only PR. It does not introduce runtime code changes.
The implementation remains in PR #10266:
The design covers:
x-amz-security-tokenfor subsequent S3 access.AssumeRole.This design does not propose replacing Kerberos daemon authentication, does not add OFS OIDC login, does not add CLI device-code login, and does not make Keycloak Authorization Services the Ozone policy
engine.
This design PR is split from the implementation PR so the design can be reviewed independently and documentation edits do not require rerunning the full implementation CI.
The operator/runtime Keycloak/Ranger guide remains in the implementation PR for now because it is tied to implementation config and runtime behavior.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15273
How was this patch tested?
This is a design-document-only PR.
The patch was checked with: