OAuth 2.0 OIDC Configuration override
Different clients may have different requirements. To meet this requirement, the authorization server in Airlock IAM offers configuration overrides.
Configuration overrides use the configuration of the authorization server as the base and allow for configuration on a particular client to override the base configuration.
The following table shows which features can profit from configuration overrides and how:
Feature | Authorization server | client |
---|---|---|
Flows and Grants | configuration applies to all clients | - |
Endpoints | configuration applies to all clients | - |
Persistency | configuration applies to all clients | - |
Scopes | default configuration for
| configuration of
overrides for
|
Claims | default token format for
| overrides for
|
PKCE | default for
| override for
|
Further information and links
- See OAuth 2.0 scopes for more information about scopes and scope processing.
- See OAuth 2.0 claims for more information about token generation and claims.
- See PKCE - Proof Key for Code Exchange for general information about PKCE.