Mapping rules for OAuth and OIDC

Security Verify Access provides default mapping rules that you can use and customize for your OAuth or OIDC deployment.

Managing OAuth 2.0 and OIDC mapping rules
Use the mapping rules to customize the methods for the OAuth 2.0 or OIDC flow.
OAuth 2.0 and OIDC mapping rule methods
You can use Java methods to customize the PreTokenGeneration and PostTokenGeneration mapping rules.
OAuth and OIDC mapping rules files
In OAuth and OpenID Connect deployments, you can use mapping rules to customize your use of Security Verify Access features.
OAuth and OIDC mapping rules actions
You can modify mapping rules to perform actions that you need for your OAuth or OIDC deployment.
Customizing OAuth tokens by updating the sample PreTokenGeneration mapping rule
You can customize the format of the tokens that are issued by your OAuth definition.
OpenID Connect mapping rules
Mapping rules allow users to customize the information that is propagated from an OpenID Connect Provider or what is consumed by a Relying Party.
Device flows verification_uri
The device flow requires the client be presented with a verification_uri.

Parent topic: OAuth 2.0 and OIDC support