EPMDEDP-17150: docs: document username_claim/username_prefix for Keycloak EKS OIDC setup#386
Merged
Conversation
…loak EKS OIDC setup Kubernetes falls back to the sub claim prefixed with the issuer URL when username_claim is unset, producing an unreadable username in kubectl output, RBAC errors, and audit logs. Document setting username_claim to preferred_username (not email, which Kubernetes rejects when email_verified is false — common for SAML-brokered upstream IdPs like Azure AD) and pinning username_prefix to "-", across the current docs, all three versioned snapshots, and the original Keycloak+EKS blog post. Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://gentle-pebble-0839af61e-386.westus2.4.azurestaticapps.net |
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
1 participant
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.
Kubernetes falls back to the sub claim prefixed with the issuer URL when username_claim is unset, producing an unreadable username in kubectl output, RBAC errors, and audit logs. Document setting username_claim to preferred_username (not email, which Kubernetes rejects when email_verified is false — common for SAML-brokered upstream IdPs like Azure AD) and pinning username_prefix to "-", across the current docs, all three versioned snapshots, and the original Keycloak+EKS blog post.