On this page:
   33.65    MDM 33.67    Realtime Export   

33.66OpenID Connect (OIC)


The OpenID Connect (OIC) configuration category includes the following configurable options:

  • Client Secret Encoding

  • Smile CDR generated Client Secret expiry duration in days

  • Issuer URL

  • Cache Authorizations (millis)

  • Rotate Refresh Token After Use

33.66.1Property: Client Secret Encoding

Property Name Client Secret Encoding
Property Key
Property Type ENUM
  • SHA256_1000_ROUND
  • SHA256_10000_ROUND
  • SHA256_100000_ROUND
  • PBKDF2_256_1000_RND
  • PBKDF2_256_10000_RND
  • PBKDF2_256_100000_RND
Description 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.
Default Value BCRYPT_12_ROUND
Example Property
module.[MODULE_ID].config.client_secret.encoding = BCRYPT_12_ROUND

33.66.2Property: Smile CDR generated Client Secret expiry duration in days

Property Name Smile CDR generated Client Secret expiry duration in days
Property Key
Property Type STRING
Description Select the expiry duration in days for Smile CDR generated client secrets. Note this value will be added to secret activation date to calculate secret expiration date during the client creation process via the REST path register-client-and-generate-secret.
Default Value 365
Example Property
module.[MODULE_ID].config.client_secret.expiry_duration_days = 365

33.66.3Property: Issuer URL

Property Name Issuer URL
Property Key
Property Type STRING
Description 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.
Default Value (no default)
Example Property
module.[MODULE_ID].config.issuer.url = 

33.66.4Property: Cache Authorizations (millis)

Property Name Cache Authorizations (millis)
Property Key
Description 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.
Default Value 3000
Example Property
module.[MODULE_ID].config.cache.authorized_tokens.millis = 3000

33.66.5Property: Rotate Refresh Token After Use

Property Name Rotate Refresh Token After Use
Property Key
Property Type BOOLEAN
Description 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.
Default Value false
Example Property
module.[MODULE_ID].config.rotate_refresh_token_after_use = false
   33.65    MDM 33.67    Realtime Export