Update anonymous sessions docs to match EA architecture guide - #1870
Open
BcnCarlos wants to merge 1 commit into
Open
Update anonymous sessions docs to match EA architecture guide#1870BcnCarlos wants to merge 1 commit into
BcnCarlos wants to merge 1 commit into
Conversation
Fixes several gaps found comparing our anonymous sessions docs against the Anonymous Sessions Architecture & Implementation Guide and the Management API OAS artifact: - anonymous-sessions.mdx: document the transfer-ticket mechanism for cross-domain session transfer (anon_transfer_token), the ROPG transfer scenario, and the lack of server-side session invalidation. Removed an unverified Auth0-Anonymous-Session header example not present in the OAS or the architecture guide. - configure-anonymous-sessions.mdx: add Dashboard instructions alongside the existing Management API steps for tenant, application, API, and client-grant configuration. Fixed the resource-server PATCH example, which included allow_anonymous_access — a field that does not exist in the Management API schema (additionalProperties: false on UpdateResourceServerRequestContent). Added the missing activate_cookie parameter and corrected the example lifetime value to match our own 30-day-or-longer best practice guidance. - configure-custom-claims-for-anonymous-sessions.mdx (new): documents Claims Mapping, which lets an API map anonymous_session.metadata fields directly into access token custom claims, since anonymous sessions have no post-login Action execution to call setCustomClaim(). Registered in manage-users.json navigation.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
Summary
Errors per inputErrors in main/docs/manage-users/sessions/anonymous-sessions.mdx
Errors in main/docs/manage-users/sessions/anonymous-sessions/anonymous-sessions-use-cases.mdx
Run on commit 9a28b02. |
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.
Summary
Reconciles
main/docs/manage-users/sessions/anonymous-sessions/*against the Auth0 Anonymous Sessions Architecture & Implementation Guide and the Management API OAS artifact. Found and fixed several gaps:anonymous-sessions.mdxanon_transfer_tokenviaurn:auth0:anon_transfer_tokenaudience) for cases where cookies get blocked (Apple ITP, cross-domain CORS).anonymous_session_tokenin the/oauth/tokenbody).Auth0-Anonymous-Sessionheader example — it does not appear in the architecture guide or the Management API OAS, and could not be confirmed as a real mechanism.configure-anonymous-sessions.mdxPATCHexample: it includedallow_anonymous_access, a field that does not exist in the Management API schema (UpdateResourceServerRequestContenthasadditionalProperties: falseand no such field).activate_cookieparameter to the tenant-settings example.1440minutes / 1 day, which undercut our own "30 days or longer" best-practice guidance).configure-custom-claims-for-anonymous-sessions.mdx(new)anonymous_session.metadata.*fields directly into access token custom claims, since anonymous sessions have nopost-loginAction execution to callsetCustomClaim().manage-users.jsonnavigation.Verification
activate_cookie,allow_anonymous_access(absent), andtoken_lifetime_for_anonymous_access_tokensagainstmain/docs/oas/management/v2/management-api-oas.jsonschemas (TenantSettingsSessionsAnonymous,UpdateResourceServerRequestContent).Known pre-existing issue (not fixed here, out of scope)
anonymous-sessions.mdxhas a "Batch and minimize metadata updates" link pointing toconfigure-anonymous-sessions#update-the-session-with-metadata, an anchor that doesn't exist in the target file. Flagging for a follow-up.Test plan
🤖 Generated with Claude Code