Consumer authentication
Offer familiar sign-in options such as Google or GitHub.
Kinde · Const
Social connections
Social connections let users sign up and sign in with existing social-account credentials. Configure a provider in Kinde’s Authentication settings, then enable it for the applications that should offer it.
How it works
Kinde social connections let users authenticate with existing accounts from providers such as Google or GitHub. An administrator adds a provider in the environment’s Authentication settings, supplies its credentials, and enables it for selected applications.
Key points
- They allow new and returning users to authenticate through credentials held by an existing social account.
- Google and GitHub are examples of supported social identity providers.
- Configuration begins in the environment’s Authentication settings.
- Use Add connection in the Social connections section to start provider setup.
- Custom OAuth 2.0 providers can be created from the same area as built-in social providers.
- The management API provides operations for creating, modifying, and removing social connections.
Common mistakes
- Deleting a social connection is irreversible, so verify the provider and environment before removing it.
Example: Record an enabled social provider
// Social connections are configured in the Kinde dashboard.
// Enable the connection for an application after saving it.
const authentication = {
provider: "Google",
enabledForApplication: true
};
console.log(authentication);Represent the provider configuration in application setup after adding it in Kinde.
When to use it
Custom OAuth integration
Connect an identity provider that is not available as a built-in option.
Application-specific sign-in
Control which applications expose a provider.
Interview questions
QWhat is a Kinde social connection?
A social connection delegates sign-up and sign-in to an existing social identity provider. In Kinde, an administrator adds the provider under Settings > Authentication, configures its credentials, and enables it for chosen applications.
Follow-up: How would you support a provider that is not listed? Add a Custom OAuth 2.0 connection and provide its authorization, token, user-info URLs, credentials, and client-authentication method.
QHow do you make a social provider available to an application?
First add the provider from the Social connections section and save it. Then configure the provider credentials and select which applications can use the connection.
Follow-up: What changes when an application uses a custom domain? The provider must receive the callback URL or URLs for those custom domains rather than only the default Kinde URL.
QHow can you integrate an unsupported OAuth provider?
Kinde supports adding Custom OAuth 2.0 connections through the same Social connections area. The setup requires provider endpoints, client credentials, and a choice of how client credentials are sent to the token endpoint.
Follow-up: Why is the client-authentication method significant? It determines the credential transmission style during the OAuth 2.0 authorization-code exchange.
Related
Custom OAuth 2.0 connectionsAuthenticationEnterprise connectionsKinde management APIGoogle social sign inGitHub social sign in