Skip to end of banner
Go to start of banner

User Authorisation with Active Directory and LDAP

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

Authorisation with LDAP allow users to get privileges and groups assigned based on a LDAP group. 

If a user belongs to more than one group, the privilege will be selected based on the priority (1 is higher priority than 10): 

Prerequisites

Configuration

Configuration items in opCommon.json

ItemExample ValueDescriptionDefault
auth_ldap_privs0/1Set to 1 to enable the feature0
auth_ldap_contextCN=Users,DC=opmantek,DC=localThe base search No defaults. Entry must be created.
auth_ldap_accadministrator@domain.localThe LDAP account to be able to searchNo defaults. Entry must be created.
auth_ldap_pswPasswordThe password for being able to searchNo defaults. Entry must be created.
auth_ldap_groupmemberOf

The attribute to lookup the group values. Must follow: 

CN=OMK Ops,CN=Users,DC=opmantek,DC=local

memberOf
auth_ldap_serverserver.domain.com:389The LDAP serverNo defaults. Entry must be created.

The mapping file

The mapping file by default, is named AuthLdapPrivs.json and it should be placed in <omk_dir>/conf.

It should contain a list of groups containing: 

  • privilege
  • level 
  • groups 
  • priority

As an example: 

{
   "OMK Admin" : {
      "privilege" : "administrator",
      "level" : "0",
      "groups": "all",
      "priority": 1
   },
   "OMK Eng" : {
      "privilege" : "engineer",
      "level" : "2",
      "groups": "SNMPSIM,GPON",
      "priority": 3
   }
}

You can find an example in <omk_dir>/install.

It is possible to change the default location/name in the configuration file opCommon.json: 

auth_ldap_privs_file


  • No labels