Third-party service access
Users need to work with an external service from an application authenticated by Kinde.
Kinde · Const
Connected apps
Kinde connected apps let users access third-party services through Kinde. Configure a provider with credentials, callback URLs, a code-facing reference key, and selected scopes.
How it works
Connected apps let users access third-party services through Kinde. You add a provider, configure its client credentials and callback URL, choose the permissions or scopes, and save the connection; the resulting reference key identifies it in application code.
Key points
- A connected app is Kinde's bridge for giving users access to an external tool or service.
- During setup, choose the provider capabilities, called scopes, that the connection may expose.
- Start management from the Connected apps area under Settings.
- Use Connect an app to begin adding a provider.
- Give the connection a reference key so application code can identify it.
- Permissions are selected separately in the Permissions tab and determine the scopes available through the connection.
Common mistakes
- Removing or changing access requires calling the documented revoke endpoint; disabling the connection alone is not the stated revocation mechanism.
Example: Store a connected-app reference key
# Connected apps are configured in the Kinde dashboard.
# After setup, use the configured reference key in your application.
CONNECTED_APP_REFERENCE_KEY="google_drive"Store the reference key you entered when configuring the connected app, then use that key in the relevant application integration.
When to use it
Scoped permissions
An integration should expose only selected provider capabilities.
Centralized integration configuration
A team wants to manage provider credentials and connection settings centrally in Kinde.
Interview questions
QHow do you configure a connected app in Kinde?
In Kinde, add a provider from Settings > Connected apps, save it, then configure its client ID, client secret, reference key, and callback URL. Finally select the required permissions in the Permissions tab and save.
Follow-up: Why should scopes be selected explicitly? They define which provider features are made available through the connection, so selecting only necessary permissions limits access.
QWhat callback URL is needed during setup?
After creating the connection, configure the provider outside Kinde using the Provider to Kinde callback URL copied from the connection. Then return to Kinde and enter the provider credentials and application callback URL.
Follow-up: What is the purpose of the Provider to Kinde callback URL? It gives the external provider the redirect destination needed to complete the connection flow with Kinde.
QWhat configuration is available for a connected app?
A reference key is entered while configuring the connection and is intended for use in application code. The connection also stores provider credentials and the scopes selected in the Permissions tab.
Follow-up: What should be reviewed when an integration needs another provider capability? Update the connection's selected permissions or scopes, then save the configuration and ensure the provider also grants them.
Related
Provider to Kinde callback URLreference keypermissionsscopes/connected apps/revokeClient IDClient secret