Set callback and redirect URLs
Get started
This is an advanced org feature that is only available on the Kinde Scale plan. Charges apply for each organization that uses advanced org features.
When you add a custom domain to an organization, it sets the domain URL for authentication to the custom domain, instead of a Kinde domain address. For example account.domain.com
instead of domain.kinde.com
.
It’s important to include a subdomain for this procedure to work. Common subdomain names include account
, id
, or auth
, e.g. account.domain.com
.
Kinde currently supports a single custom domain per organization.
account.domain.com
.Instructions will vary depending on your domain provider. Here’s the general process.
The challenge DNS record needs to remain in place after verification in order for us to renew your SSL certificate on an ongoing basis.
If the organization’s users will use social authentication to sign in, update the provider apps such as Google or GitHub to include the custom domain callback (e.g. account.example.com/login/callback
) as an authorized redirect URI. How you do this will be different for each provider you use.
Remember to also update your application’s codebase to reference the custom domain.
If you encounter any errors, such as the verification taking too long, re-check the DNS records you created on your provider site, to ensure the details are correct.
It’s important to include a subdomain for the procedure to work, e.g. account.domain.com
. If you left out the subdomain, delete the custom domain in Kinde, re-add it using the subdomain, and add the newly generated DNS details to your provider records.
When you create the DNS records be sure to match the format and details provided in Kinde.
For example, if your custom domain is account.example.com
, then:
Host = account
Record type = CNAME
Value = account.example.com
TTL = Leave as default
Routing policy = Leave as default
If you are using a multi-level subdomain, like multi.subdomain.example.com
, how you set up DNS records will depend on how your zones are set up.
The details provided in the admin console assumes the domain entered is adding a single level to your DNS zone, but if you are adding more than one level you’ll need to create others.
So if your business is multi.subdomain.example.com
and your zone is example.com
, you need to create a DNS entry for multi.subdomain
, as well as for _acme-challenge.multi.subdomain
.
If your users are already signing in through a custom domain, removing it can break their authentication experience.