<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[What does the new CIMD Domains feature do in FusionAuth?]]></title><description><![CDATA[<p dir="auto">I noticed a new <strong>CIMD Domains</strong> feature in FusionAuth and would like to understand what it does and how it can be used.</p>
<p dir="auto">Can someone provide an overview of this feature and its purpose?</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3421/what-does-the-new-cimd-domains-feature-do-in-fusionauth</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 09:45:29 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/3421.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 20 Nov 2026 21:01:33 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to What does the new CIMD Domains feature do in FusionAuth? on Sat, 21 Nov 2026 03:51:29 GMT]]></title><description><![CDATA[<p dir="auto">The <strong>CIMD Domains</strong> feature allows you to dynamically register OAuth clients using the <strong>Client ID Metadata Documents (CIMD)</strong> OAuth extension. This is not specific to MCP (Model Client Protocol), but rather is designed to support <strong>Model Context Protocol (MCP)</strong> clients—AI assistants like Claude or ChatGPT that need to connect to your MCP server.</p>
<p dir="auto"><strong>Note:</strong> This feature requires an <strong>Enterprise plan</strong> and is available since FusionAuth version <code>1.70.0</code>.</p>
<h2>What It Does</h2>
<p dir="auto">With CIMD, instead of manually registering each OAuth client in FusionAuth, the <code>client_id</code> itself 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:</p>
<ol>
<li>Fetches the client metadata document from the URL</li>
<li>Validates the document against configured CIMD domains</li>
<li>Automatically registers the client just-in-time</li>
<li>Caches the client information</li>
<li>Proceeds with the OAuth authorization flow</li>
</ol>
<h2>Why It Exists</h2>
<p dir="auto">The Model Context Protocol creates a trust challenge: AI clients like <code>claude.ai</code> or <code>chatgpt.com</code> cannot pre-register with every MCP server in existence. CIMD solves this by allowing you to trust entire <strong>origins</strong> (like <code>https://claude.ai</code>) rather than individual clients, enabling dynamic registration without manual setup for each client.</p>
<h2>How to Configure</h2>
<p dir="auto">You configure <strong>CIMD domains</strong> at the Tenant level. Each CIMD domain represents one trusted origin that clients may register from (e.g., <code>https://claude.ai</code>). You can also use a wildcard <code>*</code> to accept clients from any origin (though this cannot be mixed with specific domains).</p>
<h2>Key Constraints</h2>
<ul>
<li><strong>PKCE is required</strong> for all CIMD clients</li>
<li>Only <code>authorization_code</code> and <code>refresh_token</code> grant types are supported</li>
<li>User consent is always required (CIMD clients are treated as third-party clients)</li>
<li>Redirect URIs must exactly match what's in the client's metadata document</li>
<li>Magic links, passkeys, and IdP-initiated SAML v2 login are not supported</li>
<li>Clients must send exactly one <code>resource</code> parameter matching the domain's authorized resource URIs</li>
</ul>
<h2>Related Documentation</h2>
<ul>
<li><a href="https://fusionauth.io/docs/concepts/types/cimd-domains" rel="nofollow ugc">CIMD Domains Concepts</a> — comprehensive overview of CIMD domains and how to manage them</li>
<li><a href="https://fusionauth.io/docs/authentication/oauth/client-registration#client-id-metadata-documents" rel="nofollow ugc">OAuth Client Registration with CIMD</a> — details on how CIMD integrates with OAuth client registration</li>
<li><a href="https://fusionauth.io/docs/authentication/oauth/host-cimd-document" rel="nofollow ugc">Host a Client ID Metadata Document</a> — step-by-step guide for publishing and using CIMD documents</li>
<li><a href="https://fusionauth.io/articles/ai/mcp-connecting-software-ai" rel="nofollow ugc">Understanding Model Context Protocol</a> — background on MCP and why CIMD is important for AI integrations</li>
<li><a href="https://fusionauth.io/docs/security/clients/cimd-security" rel="nofollow ugc">CIMD Security Considerations</a> — security controls and best practices for CIMD</li>
</ul>
]]></description><link>https://fusionauth.io/community/forum/post/9183</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/9183</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Sat, 21 Nov 2026 03:51:29 GMT</pubDate></item></channel></rss>