OIDC module

Acts as an OpenID Connect Provider.

On this page, you can manage the Back-Channel Endpoints. The configuration of the Authorization Endpoint depends on the selected OIDC flow type:

• For Authorization Code Flow, click LINK.

• For Implicit Flow, click LINK.

Introduction

Can be configured in multiple instances allowing for multi tenancy.

Acts as an OpenID Connect provider. It acts as a controller mainly 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

Properties

Name	Description	Default value	Mandatory
http_context	Base URI for the endpoints.	N/A
http_port	Port	N/A
tenant_op_path	A tenant specific path part of the endpoint URIs. Example: http://127.0.0.1:8080/oidc/tenant1/token-endpoint	N/A
discovery_meta	Discovery data presented at the OpenID Configuration endpoint.	N/A
keystore	Keystore reference or json object. Used for JWT signing/validation. If no alias is configured, the first alias will be used.	N/A
rps	List of relying parties. Must include at least one relying party.	N/A
required_request_parameters	Required request parameters for the token endpoint.	["redirect_uri","code"]
code_verifier_hash_alg	Hash algorithm used for Proof Key of Code Exchange (PKCE).	"SHA-256"
enable_refresh_token	Set to true if using refresh tokens.	false
reuse_refresh_token	Set to true when the OIDC RP does not support rotating refresh tokens.	false

Example