Organization-aware APIs
Include organization context in an access token for API authorization.
Kinde · Const
Token customization
Kinde token customization lets you add preset claims and properties to application tokens. Configure it per application for access, ID, or M2M tokens in the Kinde dashboard.
How it works
Token customization lets an application choose preset claims and public properties to include in access, ID, or M2M tokens. Configure it from the application's Tokens area, select Customize for the relevant token type, choose the available claims or properties, and save.
Key points
- The feature supports preset claims and properties for access, M2M, and ID tokens.
- Begin configuration by opening the application details from Settings > Applications.
- The customization controls are located in the application's Tokens section.
- Choose Customize on the card for the token type you want to change.
- Choose which available claims and properties should be emitted.
- M2M token customization supports adding feature flags.
Common mistakes
- Do not expect standard JWT claims such as
subto be replaceable through token customization. - Properties must be marked public before they can be selected for inclusion in a token.
Example: Dashboard configuration
// No runnable code is provided because this feature is configured in Kinde's dashboard.Token customization is configured per application in Kinde rather than declared in application code.
When to use it
Client identity data
Add selected user identity data to an ID token used by a client application.
M2M feature control
Expose feature flags to a machine-to-machine integration.
Interview questions
QHow is token customization configured?
Open the application, go to Tokens, find Token customization, and choose Customize on the required token type. Select the available additional claims or properties, then save the configuration.
Follow-up: How would you include a custom claim that is not one of the available built-in choices? Use a workflow that modifies the appropriate access or ID token rather than relying on this dashboard feature.
QWhich token types can be customized?
Backend applications can customize access, ID, and M2M tokens. Frontend applications support access and ID tokens, while M2M applications support only M2M tokens.
Follow-up: What should you check before adding a property? Confirm that the property is public in its property settings.
QWhat can token customization add?
The feature provides preset additional claims and properties, such as organization name, roles, email, and external organization ID for access tokens. It can also add social identity or organizations to ID tokens and feature flags to M2M tokens.
Follow-up: Can standard JWT claims be changed? No; claims such as sub cannot be overridden through token customization.
Related
Additional claimsProperties in tokensAccess tokensID tokensM2M tokensToken customization