Versions Compared

Old Version 4

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version Current

changes.mady.by.user Chieko Sugizaki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2023.2

...

SettingPurpose
oidc.enabled=true|false

Enables or disables user authentication via OpenID Connect.

Default: false

oidc.issuer.uri=[uri]

Specifies the URI of the OpenID Connect server.

Example: oidc.issuer.uri=http://server.com/

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: openid profile offline_access

oidc.cli.mode=devicecode|certificate

Specifies the method that will be used to authenticate the user on the OpenID Connect server.

Default: devicecode

oidc.devicecode.token.file=[path]

Specifies the path to the custom token file containing user authentication information.

Example: oidc.devicecode.token.file=C:\\parasoft\\token

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=C:\\parasoft\\certificates\\client_keystore.jks

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.alias=myalias

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 -encodepass flag. The command line tool will generate an encoded string that you can use in the configuration file. 

Example: oidc.keystore.password=myPassword0987

...