docs(auth): document ADR-0069 enterprise auth hardening + SAML SSO#2405
Merged
Conversation
The hand-written auth guides predated ADR-0069 and were stale: - auth-sso.mdx: only covered OIDC; added an "Enterprise SSO (SAML 2.0)" section (Register SAML Provider action, IdP fields, SP ACS/metadata URLs, sign-in flow) and reframed the ADR-0069 note around the admin-managed Setup → SSO Providers UI. - authentication.mdx: "Key Features" listed none of the P1/P2 controls; added them and a canonical "Enterprise Authentication Hardening (ADR-0069)" settings reference (password policy / anti-abuse / enforced MFA / sessions / network + how the session-validation gate works). Reframed the stale "do not expose 2FA" caveat to point at enforced MFA + the Console remediation flow. - HARDENING.md: expanded the TL;DR auth row, added an "Authentication hardening" production-settings section, and noted the new session-control settings. - security.mdx: cross-linked authentication hardening as the first security layer and added it to the security checklist. References/* are generated from object/action metadata and self-update; not touched. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
The hand-written authentication guides predated ADR-0069 (now fully shipped) and were stale — they listed none of the P1/P2 controls and had no SAML coverage. This updates them to match what's live.
Changes
content/docs/guides/auth-sso.mdx— only covered OIDC. Added an "Enterprise SSO (SAML 2.0)" section (Register SAML Provider action, IdP fields table, SP ACS + metadata URLs, SAML sign-in flow) and reframed the ADR-0069 note around the admin-managed Setup → SSO Providers UI (no-code OIDC and SAML).content/docs/guides/authentication.mdx— "Key Features" listed none of the hardening controls. Added them and a canonical "Enterprise Authentication Hardening (ADR-0069)" settings reference (password policy / anti-abuse / enforced MFA / sessions / network) plus a note on how the shared session-validation gate works. Reframed the now-contradicted "do not expose 2FA" caveat to point at enforced MFA + the Console remediation flow.docs/HARDENING.md— expanded the TL;DR auth row, added an "Authentication hardening" production-settings section, and noted the new session-control settings in the session-lifecycle table.content/docs/guides/security.mdx— cross-linked authentication hardening as the first security layer and added it to the security checklist.content/docs/references/**are generated from object/action metadata (the newregister_saml_provideraction shows up there automatically on regen) — not hand-edited.Verification
scripts/check-doc-authoring.mjs→ clean (164 files, no bare metadata literals).<…>outside code fences (the classic MDX break).🤖 Generated with Claude Code