<?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[Topics tagged with cimd]]></title><description><![CDATA[A list of topics that have been tagged with cimd]]></description><link>https://fusionauth.io/community/forum/tags/cimd</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 09:45:39 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/cimd.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[What does the new CIMD Domains feature do in FusionAuth?]]></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 1.70.0.</p>
What It Does
<p dir="auto">With CIMD, instead of manually registering each OAuth client in FusionAuth, the client_id 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>

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
<p dir="auto">The Model Context Protocol creates a trust challenge: AI clients like claude.ai or chatgpt.com cannot pre-register with every MCP server in existence. CIMD solves this by allowing you to trust entire <strong>origins</strong> (like https://claude.ai) rather than individual clients, enabling dynamic registration without manual setup for each client.</p>
How to Configure
<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., https://claude.ai). You can also use a wildcard * to accept clients from any origin (though this cannot be mixed with specific domains).</p>
Key Constraints

<strong>PKCE is required</strong> for all CIMD clients
Only authorization_code and refresh_token grant 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 resource parameter matching the domain's authorized resource URIs

Related Documentation

<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
<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
<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
<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
<a href="https://fusionauth.io/docs/security/clients/cimd-security" rel="nofollow ugc">CIMD Security Considerations</a> — security controls and best practices for CIMD

]]></description><link>https://fusionauth.io/community/forum/topic/3421/what-does-the-new-cimd-domains-feature-do-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3421/what-does-the-new-cimd-domains-feature-do-in-fusionauth</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>