Changing auth custom domain.
Is there docs on how to do this?
I have auth.domain1 and want to do auth.domain2 instead.
I am using 2 social sign-ins only -> Apple and Google.
4 Replies
Hi Corwin,
Yes – to move your authentication from auth.domain1 to auth.domain2 while using Apple and Google sign-ins, you’ll need to update the configuration in both your social provider dashboards and in Kinde. Steps to follow: 1. Update provider settings: - Google: Add the new domain’s callback URL to your Google Cloud project (OAuth consent screen > credentials > authorized redirect URIs). - Apple: Add the new domain and callback URL in your Apple Developer portal under your Services ID configuration. 2. Update Kinde: - In Kinde Admin, go to Settings > Authentication > Social connections. - Edit your Apple and Google connections to include the new callback URLs. - Make sure both the old and new domains’ callback URLs are present if you’re running them in parallel. 3. Use your own credentials: - For production, don’t rely on Kinde’s default credentials. Enter your own Client ID and Client Secret from Apple and Google. For step-by-step instructions, you can use these guides: - Apple social sign in - Google social sign in - Managing social connections
Yes – to move your authentication from auth.domain1 to auth.domain2 while using Apple and Google sign-ins, you’ll need to update the configuration in both your social provider dashboards and in Kinde. Steps to follow: 1. Update provider settings: - Google: Add the new domain’s callback URL to your Google Cloud project (OAuth consent screen > credentials > authorized redirect URIs). - Apple: Add the new domain and callback URL in your Apple Developer portal under your Services ID configuration. 2. Update Kinde: - In Kinde Admin, go to Settings > Authentication > Social connections. - Edit your Apple and Google connections to include the new callback URLs. - Make sure both the old and new domains’ callback URLs are present if you’re running them in parallel. 3. Use your own credentials: - For production, don’t rely on Kinde’s default credentials. Enter your own Client ID and Client Secret from Apple and Google. For step-by-step instructions, you can use these guides: - Apple social sign in - Google social sign in - Managing social connections
Kinde docs
Apple social sign in
Complete guide to setting up Apple social sign-in including Apple Developer account setup, Services ID configuration, and JWT client secret generation.
Kinde docs
Add and manage social connections
Comprehensive guide to adding and managing social sign-in connections including setup, security considerations, and provider-specific configurations.
Kinde docs
Google social sign in
Step-by-step guide to setting up Google social sign-in including Google Cloud project setup, OAuth credentials, and Kinde integration.
Thanks Roshan! Can I somehow get the ability to have a second domain on Kinde during the transition period? So I have
So I can have both while moving over everyone?
Hi Corwin,
During the transition you can keep both domains active. The simplest way is to keep your current Kinde auth domain as-is, and add both
domain1 and domain2 to the allowed callback URLs in Kinde. You’ll also want to add both return URLs in your Google and Apple configurations (Apple requires verifying each domain). This allows sign-ins to work on both domains while you migrate.
If you do need to switch the actual Kinde auth domain itself (so the issuer changes from auth.domain1 to auth.domain2), a single environment can only use one custom auth domain at a time. In that case you’d either plan a cutover, or create a new Kinde organization with its own custom domain if you want to run both side by side.
This way you can choose between the easiest path (supporting both app domains under your current setup) or the more advanced path (new organization for dual domains).I cant seem to add a second domain to my acocunt
No option to in settings