Clarify Okta generic SAML integration requirements and failure modes - #3919
Open
mich-elle-luna wants to merge 2 commits into
Open
Clarify Okta generic SAML integration requirements and failure modes#3919mich-elle-luna wants to merge 2 commits into
mich-elle-luna wants to merge 2 commits into
Conversation
- Flag redisAccountMapping as required; missing/malformed values fail SAML activation and login. - Note the activating user needs ACCOUNT_ID=owner in their mapping. - Clarify how to paste the X.509 certificate. - Explain the two-part handshake between the temporary mock URLs and the Redis SP metadata update in Step 3. - Make the DNS TXT record domain-verification requirement explicit. - Warn that role values must be lowercase, with an example. - Explain why the Profile Editor custom attribute step is necessary. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Contributor
Contributor
andy-stark-redis
approved these changes
Sep 4, 2026
andy-stark-redis
left a comment
andy-stark-redis
left a comment
Contributor
There was a problem hiding this comment.
Small suggestion, but otherwise LGTM.
…ration-okta-generic.md Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
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
2 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.
Note
Low Risk
Documentation-only edits to a single Hugo page; no runtime, auth, or deployment behavior changes.
Overview
Expands the Okta (generic) SAML integration guide with prerequisite and troubleshooting detail so operators hit fewer silent failures during setup.
The intro now states that domain verification requires a Redis Cloud–provided DNS TXT record before SAML can be enabled. Configure SAML adds a note on the two-part handshake (temporary mock URLs in Okta, then replace with Redis SP metadata in Step 3).
redisAccountMappingis called out as required after the attribute statements, with a new paragraph tying Profile Editor custom attributes to what Okta actually sends in assertions.Group assignment text is corrected to
ACCOUNT_ID=role(e.g.1937217=viewer) plus a note that roles must be lowercase. Step 3 adds requirements for the activating user (ACCOUNT_ID=ownerin mapping) and how to paste the X.509 certificate without extra PEM headers unless the UI asks for them.Reviewed by Cursor Bugbot for commit 65857b9. Bugbot is set up for automated code reviews on this repo. Configure here.