OpenID Connect (OIDC)
The OpenID Connect (OIDC) configuration category includes the following configurable options:
Cache Authorizations (millis)
Client Secret Encoding
Smile CDR generated Client Secret expiry duration in days
Issuer URL
New Session for Each Flow
PKCE Plain Challenge Supported
PKCE Required
Rotate Refresh Token After Use
Smart Capabilities List
|
Cache Authorizations (millis) |
|
|
NON_NEGATIVE_INTEGER | |
If a non-zero value is supplied, the authorization server will cache successful authorizations for up to this amount of time. This means that if an Access Token is received as authentication with a request (e.g. in an Authorization header during a FHIR call) multiple times within the cache timespan, only one attempt to validate the token will be made. Using the cache can greatly improve performance on heavily loaded systems. However, manually invalidated tokens may be accepted as still being valid during the cache period so it is important to not use a value that is unnecessarily long. | |
|
|
3000
|
|
|
|
Client Secret Encoding |
|
|
ENUM | |
Values |
|
Select the hashing algorithm to use when storing client secrets. Note that the value selected here will apply only to newly created secrets, and this may be changed at any time without affecting existing secrets. See Password Hashing Algorithms for more information. | |
|
|
BCRYPT_12_ROUND
|
|
|
|
Smile CDR generated Client Secret expiry duration in days |
|
|
NON_NEGATIVE_INTEGER | |
Select the expiry duration in days for Smile CDR generated client secrets. Note this value will be added to the activation date of the secret to calculate the expiration date for the secret during the client creation process via the REST path register-client-and-generate-secret. | |
|
|
365
|
|
|
|
Issuer URL |
|
|
STRING | |
This is the URL that will be placed in OpenID Connect tokens as the iss (issuer) token. The value should be the URL to the identity server.
|
|
|
|
(no default) | |
|
|
New Session for Each Flow |
|
|
BOOLEAN | |
If enabled, every time an interactive flow is initiated the user session will be cleared. This should be set in cases where different users might access the module using the same browser, so previous authentication should not be remembered. | |
|
|
false
|
|
|
|
PKCE Plain Challenge Supported |
|
|
BOOLEAN | |
If disabled, the PKCE challenge type PLAIN will not be allowed on this server.
|
|
|
|
true
|
|
|
|
PKCE Required |
|
|
BOOLEAN | |
If this setting is enabled, the server will require the use of PKCE for all Authorization Code SMART Auth flows. Enabling this setting also disallows the use of the OAuth2 Implicit Grant type, since this flow does not support PKCE. | |
|
|
false
|
|
|
|
Rotate Refresh Token After Use |
|
|
BOOLEAN | |
If enabled, each time a refresh token is used to obtain a new access token, the refresh token will be invalidated and a new one automatically issued with the new access token. | |
|
|
false
|
|
|
|
Smart Capabilities List |
|
|
STRING_MULTILINE | |
List of Smart Capabilities to enable (See http://hl7.org/fhir/smart-app-launch/conformance.html#capability-sets); one capability per line. | |
|
|
(no default) | |
|