...
Setting | Purpose |
---|---|
oidc.enabled=true|false | Enables or disables user authentication via OpenID Connect. Default: |
oidc.issuer.uri=[uri] | Specifies the URI of the OpenID Connect server. Example: |
oidc.client.id=[user] | Specifies the ID provided by your OpenID Connect server. |
oidc.client.secret=[password] | Specifies the application's password to the OpenID Connect server. |
oidc.scopes=[list of scopes] | Defines a space-separated list of scopes, which are used during authentication to authorize access to a user's details. Default: |
oidc.cli.mode=devicecode|certificate | Specifies the method that will be used to authenticate the user on the OpenID Connect server. Default: |
oidc.devicecode.token.file=[path] | Specifies the path to the custom token file containing user authentication information. Example: |
oidc.keystore=[path] | Specifies the path to the keystore file that stores the certificate to authenticate the user on the OpenID Connect server. If only FIPS-approved algorithms are allowed, the keystore file must be in BCFKS (Bouncy Castle FIPS Keystore) format. Example: |
oidc.keystore.alias=[alias] | Specifies the alias you want to use to authenticate on the OpenID Connect server. You may need to configure this setting if your keystore file contains multiple entries. Example: |
oidc.keystore.password=[password] | Specifies the password to the the keystore file that stores the self-signed client certificate. We highly recommend that you use an encoded password to ensure successful authentication and increase the level of security. You can encode your password by running a command line instance of SOAtest with the Example: |
...