Class CustomDomainsManager

Hierarchy

  • BaseAPI
    • CustomDomainsManager

Constructors

Properties

configuration: Configuration

Methods

  • 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:

    • custom_client_ip_header
    • tls_policy

    TLS Policies:

    • recommended - for modern usage this includes TLS 1.2 only
    • compatible - compatible with older browsers this policy includes TLS 1.0, 1.1, 1.2

    Some considerations:

    • The TLS ciphers and protocols available in each TLS policy follow industry recommendations, and may be updated occasionally.
    • Do not use the compatible TLS policy unless you have clients that require TLS 1.0.

    Configure a new custom domain

    Throws

    Parameters

    Returns Promise<ApiResponse<PostCustomDomains201Response>>

  • Update a custom domain.

    These are the attributes that can be updated:

    • custom_client_ip_header
    • tls_policy
    Updating CUSTOM_CLIENT_IP_HEADER for a custom domain
    To update the custom_client_ip_header for a domain, the body to send should be:
    { "custom_client_ip_header": "cf-connecting-ip" }
    Updating TLS_POLICY for a custom domain
    To update the tls_policy for a domain, the body to send should be:
    { "tls_policy": "compatible" }

    TLS Policies:

    • recommended - for modern usage this includes TLS 1.2 only
    • compatible - compatible with older browsers this policy includes TLS 1.0, 1.1, 1.2

    Some considerations:

    • The TLS ciphers and protocols available in each TLS policy follow industry recommendations, and may be updated occasionally.
    • Do not use the compatible TLS policy unless you have clients that require TLS 1.0.

    Update custom domain configuration

    Throws

    Parameters

    Returns Promise<ApiResponse<PostCustomDomains201Response>>

  • Run 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

    Throws

    Parameters

    Returns Promise<ApiResponse<PostVerify200Response>>