Persistent Auth & Custom Domains
hi! I am trying to understand whether Custom Domains are truly the only way to have persistent auth? What I mean by persistent auth, is the user stays logged in even if they refresh the page.
In the SDK (https://kinde.com/docs/developer-tools/react-sdk/), it states this is necessary. But when I dig into it, this essentially is having me configure social logins individually and by scratch rather than using the built in social connectors? I feel like this defeats the purpose of the platform and I am trying to understand what options we have. Is this is a planned future iteration to have persistent auth without custom domains?
2 Replies
Hey @Deck thanks for asking the question
1. Custom domains are indeed the recommended way to achieve persistent authentication with Kinde, as they allow for the setting of secure, httpOnly first-party cookies on your domain. This ensures that the authentication state persists across full-page refreshes and new tabs, providing a seamless user experience.
2. Using Custom Domains also help to make the experience of your product more complete for your users, so they know that they are logging into your product and not somewhere else.
3. Its good practice to use your own social SSO connection instead of Kinde's once you are live as it will mean that users will see your brand there on the request and also means that if you need to use your social SSO connection somewhere else all the accounts are connect in the one location.
4. If you use Kinde's credentials, you will be subject to rate limiting, which can restrict the number of users who can sign in using Google within a given time frame. By using your own credentials, you can avoid these limits and ensure a smoother experience for a larger number of users.
Let me know if you have any other questions
Thanks @Andre @ Kinde you can close this!