feat: add Multiple Custom Domains (MCD) support and fix JWT verification#71
Merged
kishore7snehil merged 21 commits intomainfrom Apr 8, 2026
Merged
feat: add Multiple Custom Domains (MCD) support and fix JWT verification#71kishore7snehil merged 21 commits intomainfrom
kishore7snehil merged 21 commits intomainfrom
Conversation
…in resolution and improved session handling
…session handling in MCD mode
nandan-bhat
requested changes
Mar 2, 2026
…issuer validation and claims updates
nandan-bhat
approved these changes
Apr 8, 2026
Merged
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.
🎯 Overview
This PR adds Multiple Custom Domains (MCD) support to
auth0-server-python, enabling applications to serve multiple custom domains on the same Auth0 tenant from a single application. Additionally, this PR includes critical security fixes for JWT verification and token refresh in MCD scenarios.✨ Features
1. Multiple Custom Domains Support
Callableas domain parameter for runtime resolutionDomainResolverContextwithrequest_urlandrequest_headersExample:
2. Unified Discovery Cache (OIDC Metadata & JWKS)
OrderedDictstores both OIDC metadata and JWKS per domain3. JWT Signature Verification with Issuer Validation
_normalize_issuer()handles trailing slashes, case sensitivity, scheme differenceskid4. Domain-Specific Session Management
5. Backchannel Logout (BCLO) in MCD Mode
issagainst the resolved domain (from Host header) before signature verificationissdetermined which JWKS to use - an attacker-controlled token could choose its own verifierissin LogoutTokenClaims:issis now a first-class field onLogoutTokenClaims(previously added dynamically to the claims dict)delete_by_logout_tokenabstract docstring documents OR matching logic and iss validation for store implementors6. ID Token Verification in Custom Token Exchange
login_with_custom_token_exchangenow verifies ID token signature via JWKS (previously usedverify_signature=False)issagainst OIDC metadata issuer_verify_and_decode_jwtpath as the standard login callback🔄 Compatibility
Backward Compatible - No breaking changes for existing users.
Existing Usage (Unchanged)
New Usage (Optional)
What Changed Internally
issagainst the resolved domain before signature verification (security fix)login_with_custom_token_exchangenow verifies ID token signature and issuer (security fix)LogoutTokenClaimsmodel now includesissas an explicit field (improvement)delete_by_logout_tokenabstract docstring updated with OR matching and iss validation guidance (improvement)📊 Testing
Unit Tests
135 tests passing (
poetry run pytest), including MCD-specific tests covering domain resolution, session isolation, cache behavior, issuer normalization, migration scenarios, and BCLO issuer validationManual Integration Testing
Prerequisites:
login.brand-1.comandlogin.brand-2.comboth pointing to the same tenant)/etc/hosts:Setup:
Configure two custom domains in your Auth0 tenant (Manage Dashboard → Branding → Custom Domains)
Register callback URLs in the application:
http://brand-1.yourapp.com:3000/auth/callbackhttp://brand-2.yourapp.com:3000/auth/callbackCreate a FastAPI app with MCD:
python server.pyTest cases:
http://brand-1.yourapp.com:3000/auth/loginlogin.brand-1.com/authorizehttp://brand-2.yourapp.com:3000/auth/loginlogin.brand-2.com/authorizelogin.brand-1.comhttp://brand-2.yourapp.com:3000/profilelogin.brand-1.com/oauth/tokenServerClientwithdomain="login.brand-1.com"(string)issnot matching resolved domainissmatching resolved domainlogin_with_custom_token_exchangewith valid token📚 Documentation
examples/MultipleCustomDomains.md- Developer guide with resolver patterns and usage examples