For your auth application to work correctly and securely, you need to set up at least one custom domain name. After the set up, all requests to Prelude Auth will be routed through this domain name.Documentation Index
Fetch the complete documentation index at: https://docs.prelude.so/llms.txt
Use this file to discover all available pages before exploring further.
Domain Name Requirements
The custom domain name must be a valid domain name owned by you. It must be a subdomain of the domain name your application is hosted on. If you host your application on multiple domains, you can set up one for each domain. For example, if your application is hosted onexample.com, you can set up a custom domain name for Prelude Auth like session.example.com.
Prelude Auth uses cookies to authenticate requests. Modern web browsers block third-party cookies by default. By setting up a custom domain name that is a subdomain of the domain your application is hosted on, you can ensure that the cookies won’t be blocked.
How To Set Up a Custom Domain Name
Create a custom domain name
Perform a
POST /v2/session/apps/{appID}/domains to the Auth Management API. Ensure that the domain name is a subdomain of the domain your frontend application is hosted on.Add the CNAME record to your DNS settings
Retrieve the CNAME record from the
cname_record field in the response and add it to your DNS settings for your domain name. This step varies depending on your DNS provider.Verify the custom domain name
Perform a
POST /v2/session/apps/{appID}/domains/{domainID}/verify to the Auth Management API. Prelude will automatically try to verify the CNAME record, and issue an SSL certificate for your domain name.