First UAP update#81
Closed
avanscoy wants to merge 15 commits into
Closed
Conversation
HVish
added
the
main-docs
Contributor
nick-gagliardi
left a comment
nick-gagliardi
left a comment
There was a problem hiding this comment.
LG! Few minor suggestions
| 1. Select an existing UAP or creaete a new one. For a new UAP: | ||
| a. Add a name. | ||
| b. Review mappings to ensure the profile attributes are mapping to your preferred Auth0 attributes. | ||
| [UAP mapping Authentication > Enterprise > Self-Service](/main/images/cdy7uua7fh8z/Authenticate > Enterprise > Self-Service > UAP.png) |
Contributor
Author
There was a problem hiding this comment.
From the deployment, it looks like it is, but I'll recheck it. Thanks for catching this!
| * **Required**: When set to Required, customer admins must verify their domain when setting up SSO. They will not be able to enable their connection until verification is complete. | ||
| 8. Under **Metadata**, add up to 10 metadata associated with the connection. | ||
| 9. Review your access ticket configuration for accuracy. Then, select **Create Ticket**. | ||
| 9. Under **Metadata**, add up to 10 metadata associated with the connection. |
Contributor
There was a problem hiding this comment.
nit: 10 metadata items? Reads odd to me as-is, but feel free to ignore.
| 6. Review your access ticket configuration for accuracy. Then, select **Create Ticket**. | ||
| 7. Under **Time to Live**, set an expiration period for the access ticket in seconds. By default, time to live is set to 432000 seconds (which equals five days). | ||
|
|
||
| A. Time to Live determines how long an access ticket URL is active **before** a customer admin launches the self-service assistant. It does not determine how long the customer admin has access to the assistant after it’s been launched. The expiration of the self-service assistant itself is 5 hours and cannot be configured. |
Contributor
There was a problem hiding this comment.
Should 5 be written as "five" according to style guide?
Contributor
Author
There was a problem hiding this comment.
There's three instances in this doc! Good call.
…/manage-self-service-sso.mdx Co-authored-by: Nick Gagliardi <133918568+nick-gagliardi@users.noreply.github.com>
…/manage-self-service-sso.mdx Co-authored-by: Nick Gagliardi <133918568+nick-gagliardi@users.noreply.github.com>
…/manage-self-service-sso.mdx Co-authored-by: Nick Gagliardi <133918568+nick-gagliardi@users.noreply.github.com>
…/manage-self-service-sso.mdx Co-authored-by: Nick Gagliardi <133918568+nick-gagliardi@users.noreply.github.com>
BcnCarlos
reviewed
Oct 1, 2025
Contributor
Author
|
Issues with GPG keys. Closing PR to start with a fresh one |
lrzhou25
added a commit
that referenced
this pull request
Apr 30, 2026
* feat: update MCP quickstart for On-Behalf-Of Token Exchange Updates the "Call Your API on a User's Behalf" quickstart to reflect the new On-Behalf-Of (OBO) Token Exchange implementation. JavaScript changes (PR #79): - Update sample folder: fastmcp-mcp-on-behalf-of-tokenexchange-js - Replace Custom Token Exchange with On-Behalf-Of terminology - Simplify environment variables (remove MCP_AUTH0_SUBJECT_TOKEN_TYPE) - Update token exchange: exchangeTokenOnBehalfOf() using getTokenOnBehalfOf() - Simplify MCP_AUTH0_EXCHANGE_SCOPE to "read:private" Python changes (PR #81): - Update sample folder: fastmcp-mcp-on-behalf-of-tokenexchange-python - Replace Custom Token Exchange with On-Behalf-Of terminology - Update token exchange: exchange_token_on_behalf_of() using get_token_on_behalf_of() Additional improvements: - Add rate limit note for Auth0 for AI Agents add-on - Add client grant configuration instructions - Add OBO token exchange enablement component - Update prerequisites with OBO-specific requirements Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Edits * Removed OBO token exchange prereq * Addressed Patrick's feedback * Final copyedits * Copyedits * Updated Callout --------- Co-authored-by: Claude Opus 4.7 <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
4 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.
By submitting a PR to this repository, you agree to the terms within the Auth0 Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.
Description
References
Testing
Checklist