...
The following table lists OMK configuration options and the type of authentication which it works with.
Method | Description |
---|---|
ldap | OMK will use the configured LDAP server to perform authentication Config: |
ldaps (secure) | OMK will use the configured LDAP server to perform authentication auth_ldaps_server => 'host[:port]' |
ms-ldap | OMK will use the configured Microsoft Active Directory (LDAP) server to perform authentication Config: |
ms-ldaps (secure) | OMK will use the configured Microsoft Active Directory (LDAP) server to perform authentication Config: |
radius | OMK will use the configured radius server (Cisco ACS or Steel Belted Radius for example) Config: |
tacacs | OMK will use the configured Tacacs+ server (Cisco ACS for example) Config: |
htpasswd | OMK will use the users defined in the OMK Users file, by default /usr/local/omk/conf/users.dat. Very often /usr/local/omk/conf/users.dat is a symlink pointing to /usr/local/nmis8/conf/users.dat. The htpasswd user file may be changed by altering the auth_htpasswd_file key in the opCommon.nmis authentication hash. |
token | Delegated authentication by token as described here: Delegated Authentication |
Configuration of the External Authentications
...
Warning |
---|
Authentication methods are evaluated in sequence. The first method that returns successful authentication terminates the authentication process. If a method returns an unsuccessful authentication, the process does not terminate, the next authentication method will be evaluated. Consider the following scenario when provisioning authentication for OMK applications.
|