Open
Conversation
kishore7snehil
requested changes
Feb 25, 2026
kishore7snehil
requested changes
Feb 25, 2026
|
Does this support support simple |
Contributor
Author
No. It doesn't support |
| audience?: string; | ||
| codeVerifier: string; | ||
| originDomain?: string; | ||
| originIssuer?: string; |
Member
There was a problem hiding this comment.
Why are these called originDomain and originIssuer and in the sessionData domain and issuer ?
Contributor
Author
There was a problem hiding this comment.
We use different names because they are for different moments. originDomain and originIssuer are saved only for the current login flow, so we can safely handle the callback.
domain and issuer are saved in the user session after login succeeds, and are used later for normal session actions like getting tokens and logout.
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.
Summary
This PR adds MCD support to
@auth0/auth0-server-js, enabling per-request domain resolution while preserving single‑instance SDK usage. It also addsdiscovery/JWKScaching in@auth0/auth0-auth-js.Changes
domaincan now be a resolver function. Resolver mode requiresstoreOptionsper call so the SDK can select the correct domain.domain/issuerare persisted and used fortoken exchange,refresh, andlogout; issuer validation prevents cross‑tenant mixups.if authorizationParams.scopeis overridden,openidis enforced soissis present during callback.auth0-auth-jsnow uses LRU + in‑flight de‑dupe to avoid redundantdiscovery/JWKS fetches.Usage example
MCD behavior notes
storeOptionscan cause the resolver to return no domain and fail the request.Documentation