Skip to content

io.helidon.security.providers.oidc.common.OidcConfig

Description

Open ID Connect configuration

Configuration options

KeyTypeDefaultDescription
access-token-ip-checkBooleantrueWhether to check if current IP address matches the one access token was issued for
audienceStringAudience of issued tokens
authorization-endpoint-uriURIURI of an authorization endpoint used to redirect users to for logging-in
base-scopesStringopenidConfigure base scopes
check-audienceBooleantrueConfigure audience claim check
client-credentials-configClientCredentialsConfigSet the configuration related to the client credentials flow
client-idStringClient ID as generated by OIDC server
client-secretStringClient secret as generated by OIDC server
client-timeout-millisDuration30000Timeout of calls using web client
cookie-domainStringDomain the cookie is valid for
cookie-encryption-enabledBooleanfalseWhether to encrypt token cookie created by this microservice
cookie-encryption-id-enabledBooleantrueWhether to encrypt id token cookie created by this microservice
cookie-encryption-nameStringName of the encryption configuration available through Security#encrypt(String, byte[]) and Security#decrypt(String, String)
cookie-encryption-passwordList<String>Master password for encryption/decryption of cookies
cookie-encryption-refresh-enabledBooleantrueWhether to encrypt refresh token cookie created by this microservice
cookie-encryption-state-enabledBooleantrueWhether to encrypt state cookie created by this microservice
cookie-encryption-tenant-enabledBooleantrueWhether to encrypt tenant name cookie created by this microservice
cookie-http-onlyBooleantrueWhen using cookie, if set to true, the HttpOnly attribute will be configured
cookie-max-age-secondsLongWhen using cookie, used to set MaxAge attribute of the cookie, defining how long the cookie is valid
cookie-nameStringJSESSIONIDName of the cookie to use
cookie-name-id-tokenStringJSESSIONID_2Name of the cookie to use for id token
cookie-name-refresh-tokenStringJSESSIONID_3The name of the cookie to use for the refresh token
cookie-name-stateStringJSESSIONID_3The name of the cookie to use for the state storage
cookie-name-tenantStringHELIDON_TENANTThe name of the cookie to use for the tenant name
cookie-pathString/Path the cookie is valid for
cookie-same-siteSameSiteLAXWhen using cookie, used to set the SameSite cookie value
cookie-secureBooleanfalseWhen using cookie, if set to true, the Secure attribute will be configured
cookie-useBooleantrueWhether to use cookie to store JWT between requests
corsCrossOriginConfigAssign cross-origin resource sharing settings
decryption-keysConfiguration for decryption-keys
force-https-redirectsBooleanfalseForce HTTPS for redirects to identity provider
frontend-uriStringFull URI of this application that is visible from user browser
header-tokenTokenHandlerA TokenHandler to process header containing a JWT
header-useBooleantrueWhether to expect JWT in a header field
id-token-signature-validationBooleantrueWhether id token signature check should be enabled
identity-uriURIURI of the identity server, base used to retrieve OIDC metadata
introspect-endpoint-uriURIEndpoint to use to validate JWT
issuerStringIssuer of issued tokens
max-redirectsInteger5Configure maximal number of redirects when redirecting to an OIDC provider within a single authentication attempt
oidc-metadataConfiguration for oidc-metadata
oidc-metadata-well-knownBooleantrueIf set to true, metadata will be loaded from default (well known) location, unless it is explicitly defined using oidc-metadata-resource
optional-audienceBooleanfalseAllow audience claim to be optional
outbound-typeOidcOutboundTypeUSER_JWTType of the OIDC outbound
pkce-challenge-methodPkceChallengeMethodS256Proof Key Code Exchange (PKCE) challenge creation method
pkce-enabledBooleanfalseWhether this provider should support PKCE
proxy-portInteger80Proxy port
query-id-token-param-nameStringid_tokenName of a query parameter that contains the JWT id token when parameter is used
query-param-nameStringaccessTokenName of a query parameter that contains the JWT access token when parameter is used
query-param-tenant-nameStringh_tenantName of a query parameter that contains the tenant name when the parameter is used
query-param-useBooleanfalseWhether to use a query parameter to send JWT token from application to this server
redirectBooleanfalseBy default, the client should redirect to the identity server for the user to log in
redirect-attempt-paramStringh_raConfigure the parameter used to store the number of attempts in redirect
redirect-uriString/oidc/redirectURI to register web server component on, used by the OIDC server to redirect authorization requests to after a user logs in or approves scopes
scope-audienceStringAudience of the scope required by this application
server-typeString@defaultConfigure one of the supported types of identity servers
sign-jwkConfiguration for sign-jwk
tenantsTenantConfigConfigurations of the tenants
token-endpoint-authClientAuthenticationCLIENT_SECRET_BASICType of authentication to use when invoking the token endpoint
token-endpoint-uriURIURI of a token endpoint used to obtain a JWT based on the authentication code
token-signature-validationBooleantrueWhether access token signature check should be enabled
validate-jwt-with-jwkBooleantrueUse JWK (a set of keys to validate signatures of JWT) to validate tokens
webclientWebClientWebClient configuration used for outbound requests to the identity server. This configuration sets the values to the OIDC WebClient default configuration

Deprecated Options

KeyTypeDefaultDescription
proxy-hostStringProxy host to use
proxy-protocolStringhttpProxy protocol to use when proxy is used
relative-urisBooleanfalseCan be set to true to force the use of relative URIs in all requests, regardless of the presence or absence of proxies or no-proxy lists

Dependent Types

Usages


See the manifest for all available types.