What does the new CIMD Domains feature do in FusionAuth?
-
I noticed a new CIMD Domains feature in FusionAuth and would like to understand what it does and how it can be used.
Can someone provide an overview of this feature and its purpose?
-
The CIMD Domains feature allows you to dynamically register OAuth clients using the Client ID Metadata Documents (CIMD) OAuth extension. This is not specific to MCP (Model Client Protocol), but rather is designed to support Model Context Protocol (MCP) clients—AI assistants like Claude or ChatGPT that need to connect to your MCP server.
Note: This feature requires an Enterprise plan and is available since FusionAuth version
1.70.0.What It Does
With CIMD, instead of manually registering each OAuth client in FusionAuth, the
client_iditself is an HTTPS URL that points to a JSON document describing the client (its name, redirect URIs, and other metadata). When a user initiates a login flow, FusionAuth:- Fetches the client metadata document from the URL
- Validates the document against configured CIMD domains
- Automatically registers the client just-in-time
- Caches the client information
- Proceeds with the OAuth authorization flow
Why It Exists
The Model Context Protocol creates a trust challenge: AI clients like
claude.aiorchatgpt.comcannot pre-register with every MCP server in existence. CIMD solves this by allowing you to trust entire origins (likehttps://claude.ai) rather than individual clients, enabling dynamic registration without manual setup for each client.How to Configure
You configure CIMD domains at the Tenant level. Each CIMD domain represents one trusted origin that clients may register from (e.g.,
https://claude.ai). You can also use a wildcard*to accept clients from any origin (though this cannot be mixed with specific domains).Key Constraints
- PKCE is required for all CIMD clients
- Only
authorization_codeandrefresh_tokengrant types are supported - User consent is always required (CIMD clients are treated as third-party clients)
- Redirect URIs must exactly match what's in the client's metadata document
- Magic links, passkeys, and IdP-initiated SAML v2 login are not supported
- Clients must send exactly one
resourceparameter matching the domain's authorized resource URIs
Related Documentation
- CIMD Domains Concepts — comprehensive overview of CIMD domains and how to manage them
- OAuth Client Registration with CIMD — details on how CIMD integrates with OAuth client registration
- Host a Client ID Metadata Document — step-by-step guide for publishing and using CIMD documents
- Understanding Model Context Protocol — background on MCP and why CIMD is important for AI integrations
- CIMD Security Considerations — security controls and best practices for CIMD
-
D dan has marked this topic as solved