docs(saml): document request correlation, replay refusal, and IdP-initiated out of scope#162
Merged
Merged
Conversation
…tiated being out of scope The P0-2 correlation fix (#160) is admin-visible in two ways this doc did not cover: SAML login is now strictly SP-initiated (an IdP-initiated, unsolicited Response is refused, because the InResponseTo correlation is what enforces replay protection), and the ACS can now redirect to new error codes. - 'What flows through': add the correlation + single-use step. - 'Out of scope': state IdP-initiated SSO is not supported, with the reason. - 'Troubleshooting': explain saml-unsolicited / saml-unknown-request / saml-replayed / saml-provider-mismatch and their usual causes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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.
Documentation follow-up to #160 / #161 (SAML request correlation, P0-2). The fix is
admin-visible in two ways
docs/admin/saml-federation.mddid not cover, and thisbrings the doc in line with the shipped behaviour.
What changed
Response — started from the IdP's app dashboard, with no
InResponseTo— isrefused, because that correlation is what enforces replay protection. Added to
Out of scope (v1) with the reason, so an admin doesn't wire an IdP-initiated
tile that silently fails.
signature validation and audience check.
saml-unsolicited/saml-unknown-request(IdP-initiated, or the 15-minutecorrelation window elapsed, or app instances not sharing a database),
saml-replayed(back/refresh on the ACS POST, or an actual replay),saml-provider-mismatch(wrong<slug>in the ACS URL given to the IdP).Prose only — no internals (the store, optimistic concurrency) leak into the
admin doc. Roadmap and glossary checked; nothing else references the changed
behaviour.
🤖 Generated with Claude Code