Versions Compared

Old Version 22

changes.mady.by.user John Sinclair

Saved on

compared with

New Version 23

changes.mady.by.user Mitchell Saunders

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

  1.  OMK First authentication method: LDAP
  2.  OMK Second authentication method: htpasswd
  3.  User Bob has an LDAP account and has a user in the htpasswd users file.
  4.  User Bob leaves the company
  5.  The IT department removes Bob's LDAP account assuming he will no longer be able to access corporate systems.
  6.  Bob will still be able to access OMK applications because there is a user Bob in the htpasswd user file.

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
title/usr/local/omk/conf/opCommon.json
"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.

Related Topics