Table of Contents |
---|
...
Key | Description | Example | Comment |
---|---|---|---|
auth_htpasswd_file | Location of the password file | ||
auth_htpasswd_encrypt | Enable encrypted passwords | Default is 1. Plain text passwords are checked ONLY if value is 0 or 'plaintext' |
ldap
The Opmantek products will use the configured LDAP server to perform authentication.
...
To configure the use of openaudit authentication the following items must be configured:
Key | Description | Example | Comment |
---|---|---|---|
oae_server | IP address of the Open-AudIT server | 1.2.3.4 | The link to Open-AudIT for internal connections. Should always be the original value unless explicitly directed by Opmantek to be changed. |
oae_type | Unused in on-premise installations. | ||
oae_cloud_server | cloud server URL | Unused in on-premise installations. | |
omk_ua_insecure | Validation for editing remote nodes | 0 or 1 | Allows insecure (self-signed) SSL certificates |
openid_connect
Opmantek products use OKTA's OpenID Connect for authentication. In the authentication > auth_method_1 entry of opCommon.json, use the openid_connect. For more information, see OKTA OpenID authentication.
...
The Opmantek products support a new authentication method called token,
which offers delegated authentication. This enables an external party to pre-authenticate a user, who can access the Opmantek products without having to log in with username and password.
Key | Description | Example | Comment |
---|---|---|---|
auth_token_key | One or more shared keys | extusr-1Kf!yVXt8TrP9zi | |
auth_token_maxage | The maximum length of time a token will remain valid. Must be a positive number, and defines how long a token remains valid after creation (in seconds). | 60 | If not present, the default of 300 seconds is used. |
For more information on how to generate and log in with a token, see Delegated Authentication.
...