Custom domains
Custom sign-in domains, imported SAML ACS aliases and the provisioning they require.
Host-aware imported SAML ACS aliases are implemented on the primary edge. An alias is an exact registered broker hostname plus escaped ACS path. The host must already belong to the environment, have broker purpose, be active and have verified ownership. Destination, recipient and audience checks remain strict; metadata uses the registered URLs.
This supports Lever A migration once the required host binding exists. It does not provision DNS, certificates or customer domains. Hosted custom portal, broker and SCIM provisioning remains separate work. No general custom-host authorize, OIDC or test flow is promised by this SAML alias behavior.
Use exact configuration produced for your environment. Do not substitute an arbitrary vanity hostname into authorize URLs, callback settings or token issuer validation. Copy the actual old ACS and SP entity ID; do not derive vendor-specific paths.
Custom sign-in domains
Section titled “Custom sign-in domains”A custom domain of type signin (Pro and above) is a hostname for the hosted login. After verification the sign-in pages are served on it and it is accepted as a sign-in API origin for its own environment only. Making it the environment’s active sign-in host also makes it the passkey relying party for new passkeys; see choose the active sign-in host.
Sign-in and SCIM on one hostname
Section titled “Sign-in and SCIM on one hostname”A custom domain of type broker_scim (Business and above) serves sign-in and SCIM on one hostname, as a vendor that did both on one host did (for example a self-hosted Polis on sso.example.com). Paths under /scim/ and the legacy SCIM base paths of imported directories reach SCIM only; every other path reaches sign-in only. Like the other types it is registered with your environment, verified by DNS and serves traffic only for its own environment. A plan that does not include the type answers plan_limit_reached.
Use it when you migrate from such a vendor and want the customer’s existing SCIM base URL to keep working. The import plan lists each hostname to add, with its type, in plan.custom_hostnames; see from Polis.
Check a retained ACS
Section titled “Check a retained ACS”- Confirm the hostname is a ready, verified broker host belonging to the same environment.
- Preserve the exact registered escaped path and explicit SP entity ID. A matching host with a different path is not the same ACS.
- Ensure the chosen preferred ACS is present in the connection’s legacy ACS list. The flow binds its callback to that selected host and path.
- Test the real arrival URL: strict destination, recipient and audience validation still applies. Shared paths additionally require unambiguous issuer routing within the environment.
These aliases preserve configured SAML addresses; they do not turn an old provider-owned hostname into a customer-controlled domain. Use Lever B or C when the host or private-key dependency cannot be retained.
Customer custom domains have no Stage-1 standby coverage. The oauthcat.com standby origins are a separate outage path. See standby route behavior and the API reference.