Hi team, I'm looking at setting up a custom domain for my descope project. I have a production web app that is integrated with descope via the React SDK. Should I expect any breaking changes when configuring the custom domain? Or is the custom-domain purely additive and things will continue to work as is with descope-based urls?

Hi, I'm Descope's AI assistant. I've put together an initial response below based on your question. What Gets Affected When you configure a custom domain in the Descope Console, the following settings are directly impacted: • Approved Domains: The domains authorized to interact with Descope SDK/API • Cookie Domain: Scope of the refresh token cookie changes to your custom domain • OAuth Callback URL & Callback Domain: Must be updated in each OAuth provider (e.g. Google, Facebook) • Passkey Top-Level Domain: Passkeys get bound to the new custom domain • Base URL: The SDK's base URL for all API interactions changes • SAML ACS URL: SAML assertions for tenant SP configurations will reflect the new domain Required Code Update (React SDK) You'll need to update your

AuthProvider

to pass the new `baseUrl`:

<AuthProvider projectId="__ProjectID__" baseUrl="https://auth.app.example.com">

Without this change, your app will continue pointing to the old Descope URLs, and continued behavior is not guaranteed once a custom domain is configured.

^ is this true?

Hey David; yeah, that is generally correct. React SDK won't go through the custom domain until

baseUrl

prop is set. You'll need to also update the callback URIs with OAuth providers. More details on that here Most stuff is updated automatically, but some things require manual changes. The page I linked above has all the info you need 🙂