SDK environment configuration
Configure a Kinde SDK in a server application.
Kinde · Pipe
KINDE_ISSUER_URL stores the HTTPS domain of the Kinde tenant that issues tokens. Backend SDKs or JWT validators use it to verify that tokens come from the expected issuer.
KINDE_ISSUER_URL is an environment variable containing the Kinde issuer domain. SDKs and backend token-validation code use this value to identify the issuer against which tokens should be validated.
KINDE_ISSUER_URL=https://<your_kinde_subdomain>.kinde.com| Name | Type | Description |
|---|---|---|
KINDE_ISSUER_URL | environment variable | HTTPS URL of the Kinde tenant or configured custom domain that issues tokens. |
The configured issuer URL is supplied to the Kinde SDK or JWT validator; it does not itself return a runtime value.
KINDE_ISSUER_URL=https://your-kinde-subdomain.kinde.comSet the variable to your Kinde issuer domain and load it through your framework's configuration.
Configure a Kinde SDK in a server application.
Validate access tokens in a custom backend.
Move an application from a Kinde subdomain to a custom production domain.
KINDE_ISSUER_URL identifies the Kinde domain that acts as the token issuer. Backend validation uses this issuer URL when checking a token's issuer and related claims.
Follow-up: What must change after moving to a custom domain? Update KINDE_ISSUER_URL and other relevant configuration to the exact custom domain.
Set it to the HTTPS URL for the Kinde subdomain assigned to the application, such as https://your-kinde-subdomain.kinde.com. Framework-specific setup pages show the variable alongside the other required application settings.
Follow-up: How should the value differ between local and production environments? Each environment should use the issuer domain configured for that environment.
A backend can pass KINDE_ISSUER_URL to token validation and verify the JWT's issuer, audience, expiry, and signature. The issuer URL therefore helps ensure the token came from the expected Kinde tenant.
Follow-up: What additional claim is especially relevant when authorizing access? Read and enforce the token's permissions claim after successful validation.
KINDE_CLIENT_IDKINDE_CLIENT_SECRETKINDE_SITE_URLKINDE_HOSTpermissions claim