OIDC
Acts as an OpenID Connect Provider.
Introduction
Can be configured in multiple instances allowing for multi tenancy.
Acts as an OpenID Connect provider. It acts as a controller for issuing Json Web Tokens (JWT). Typically the configured authenticator is the first point of contact coming from an OpenID Connect Relying Party, requesting identification.
Fortified Integrity have achieved certifications for five OpenID Provider conformance profiles. Read more about these profiles here: https://openid.net/certification/
OpenID Connect Provider Configuration
Module name: OIDCModule
Name | Description | Default value | Mandatory |
---|---|---|---|
| Base URI for the endpoints. | N/A | |
| Port | N/A | |
| A tenant specific path part of the endpoint URIs. Example: http://127.0.0.1:8080/oidc/tenant1/token-endpoint | N/A | |
| Discovery data presented at the OpenID Configuration endpoint. | N/A | |
| Keystore reference or json object containing key store configuration. Used for JWT signing. | N/A | |
| Keystore password. | N/A | |
| Keystore alias. | N/A | |
| N/A | ||
| Required request parameters for the token endpoint. |
| |
| Hash algorithm used for Proof Key of Code Exchange (PKCE). |
| |
| Set to |
|
Relying party Configuration
Name | Description | Default value | Mandatory |
---|---|---|---|
| Used for identifying and authenticating the client. | N/A | |
| Used for identifying and authenticating the client. | N/A | |
| Pipe reference. Pipe is run after user authentication. Used for collecting user data. | N/A | |
| Redirect location where the authorization code or JWT should be sent. | N/A | |
| Redirect location after logout. | N/A |
Last updated