N-Central – LDAP Integration and Troubleshooting

Last Updated: November 9th, 2020/Published On: March 21st, 2016/By /Views: 4509/

To integrate Active Directory (LDAP) Users into N-Central:

  1. Forward port 389 through the customer firewall to their domain controller (restrict the source to proactive.rmtt.com & set to fwd any port)
    1. On a pfSense you can create an Alias, then use that Alias for the NAT Rule
  2. Navigate to Customer Level at proactive.rmtt.com (top left will be green with customer’s name)
  3. Click Administration > User Management > SSO Providers  
  4. Add > Microsoft Active Directory and fill out server details
    1. Under Name, type customer name-AD (ex: Coet-AD)
    2. Domain = domain name
    3. Server 1: Public IP or Public FQDN
    4. Base DN is easiest found using dsquery on the customer server. Make sure you use a user account in the same organizational unit as all the other user accounts. Leave out CN=username (in this example superman), so the entry would be OU=SBSUsers,OU=Users,OU=MyBusiness,DC=cc,DC=local NCentral LDAP2
    5. Enter Domain Admin creds and select Test Connection. If DA creds change often, create another domain admin account for this item or you will need to change password here anytime it’s changed on server side.

                   NCentral LDAP3

 

 

TROUBLESHOOTING

If you change the domain admin creds that are tied to the user account you bind to LDAP with, you will need to follow these steps:

  1. Change password under Admin > User Management > SSO Providers, hit Test/Save
  2. Go to SO Level (for RMTT users)/Customer Level for individual clients and then click User Accounts
  3. Select All, then click Unlock
  4. Users should be able to login again

 

Categories: Product SpecificTags: , , ,

Table of Contents