OpenID Connect (OIC)
The OpenID Connect (OIC) configuration category includes the following configurable options:
Client Secret Encoding
Issuer URL
Cache Authorizations (millis)
|
|
|
| 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
|
|
| Yes |
|
|
|
| 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) | |
| No |
|
|
|
| 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
|
|
| Yes |