...
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.
|
NMIS9 notes
From nmis9NMIS9, changes will instead need to be made to the opCommon.json configuration file (located in /usr/local/omk/conf/opCommon.json. Also, because ). As we are using .json format files instead of .nmis, the format of the commands attributes to use is slightly different. See below for an example using tacacsTACACS:
Code Block |
---|
"auth_tacacs_server" : "host:port", "auth_tacacs_secret" : "secret", |
An example of how to integrate integrating your ms-ldap with your NMIS9 opCommon.json setup with OMK is below. Ensure you have also included ms-ldap as in one of the auth_methods:
Code Block | ||
---|---|---|
| ||
"authentication" : {
...
"auth_ms_ldap_server" : "IP_ADDRESS_OF_YOUR_MS_LDAP_SERVER", #eg. 192.168.1.22
"auth_ms_ldap_dn_acc" : "svc_omk_admin", #you should only need to use the username of the user here
"auth_ms_ldap_dn_psw" : "password_of_the_dn_acc_above",
"auth_ms_ldap_attr" : "sAMAccountName",
"auth_ms_ldap_base" : "OU=Network Admins,DC=contoso,DC=local",
... |
Once you have saved the updated opCommon.json configuration, you will then need to restart the omkd daemon.