Protected
configurationOptional
initOverrides: InitOverrideDelete a custom domain and stop serving requests for it. Delete custom domain configuration
Optional
initOverrides: InitOverrideRetrieve a custom domain configuration and status. Get custom domain configuration
Optional
initOverrides: InitOverrideRetrieve details on custom domains. Get custom domains configurations
Optional
initOverrides: InitOverrideProtected
requestOptional
initOverrides: RequestInit | InitOverrideFunctionUpdate a custom domain.
These are the attributes that can be updated:
custom_client_ip_header
for a domain, the body to
send should be:
{ "custom_client_ip_header": "cf-connecting-ip" }
tls_policy
for a domain, the body to send should be:
{ "tls_policy": "compatible" }
TLS Policies:
Some considerations:
compatible
TLS policy unless you have clients that require TLS 1.0.Update custom domain configuration
Optional
initOverrides: InitOverrideRun the verification process on a custom domain.
Note: Check the status
field to see its verification status. Once verification is complete, it may take up to 10 minutes before the custom domain can start accepting requests.
For self_managed_certs
, when the custom domain is verified for the first time, the response will also include the cname_api_key
which you will need to configure your proxy. This key must be kept secret, and is used to validate the proxy requests.
Learn more about verifying custom domains that use Auth0 Managed certificates. Learn more about verifying custom domains that use Self Managed certificates.
Verify a custom domain
Optional
initOverrides: InitOverride
Create a new custom domain.
Note: The custom domain will need to be verified before it will accept requests.
Optional attributes that can be updated:
TLS Policies:
Some considerations:
compatible
TLS policy unless you have clients that require TLS 1.0.Configure a new custom domain
Throws