HelidonHelidon4.5.2

io.helidon.security.providers.oidc.common.TenantConfig

Description

Open ID Connect tenant configuration

Configuration options

KeyTypeDefaultDescription
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-idStringClient ID as generated by OIDC server
client-secretStringClient secret as generated by OIDC server
client-timeout-millisDuration30000Timeout of calls using web client
decryption-keysConfiguration for decryption-keys
identity-uriURIURI of the identity server, base used to retrieve OIDC metadata
introspect-endpoint-uriURIEndpoint to use to validate JWT
issuerStringIssuer of issued tokens
nameStringName of the tenant
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
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
token-endpoint-authClientAuthenticationCLIENT_SECRET_BASICType of authentication to use when invoking the token endpoint. With CLIENT_SECRET_BASIC, credentials are sent only to POST requests on the resolved token endpoint scheme, host, and path and, when JWT introspection is used, to POST requests on the resolved introspection endpoint scheme, host, and path
token-endpoint-uriURIURI of a token endpoint used to obtain a JWT based on the authentication code
validate-jwt-with-jwkBooleantrueUse JWK (a set of keys to validate signatures of JWT) to validate tokens

Usages


See the manifest for all available types.

Copyright © 2018, 2026 Oracle and/or its affiliates.