Network Management / (OpenView-NNM) Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

NNM LDAP Integration | Not logging in

SOLVED
Go to solution
TMS
Member

NNM LDAP Integration | Not logging in

I am trying to perform an AD integration

 

Microsoft AD is in place 

 

I am able to retrieve data from AD using LDAP browser 

with user and server data on 389 

baseCtxDN=CN=Users,DC=com,DC=co

 

But in NNM console I am not able to login to test authentication

  

#############

 -diagnose output. 

#############

A default user role "guest" will be added to all authenticated users who provide
a correct username and password.

=========================================================
= LDAP Appears to be Properly Configured
=========================================================

=========================================================
= Finding all Users for Incident Assignment from LDAP service
=========================================================

!!!!!!!!!!!!!!!!!!!!!!!! NOTE !!!!!!!!!!!!!!!!!!!!!!!
! LDAP Appears to be Misconfigured for Incident Assignment.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

 #############

 

Any ideas / solution would be highly appreciated 

2 REPLIES
mostafa_hassan
Esteemed Contributor

Re: NNM LDAP Integration | Not logging in

 

 

you need to check LDAP.conf , again ,


java.naming.provider.url=ldap://Domainserver.dns.com:389/
baseCtxDN=OU=OrGUNIT,OU=OrGUNIT,DC=Domainserver,DC=dns,DC=com
rolesCtxDN=CN=UserGroup,OU=ORGUnit,OU=OrGUNIT,DC=Domainserver,DC=dns,DC=com
bindDN=Domainserver\\activedirectoryuser
bindCredential=Password
defaultRole=guest (Rule for who will login in by default)
baseFilter=sAMAccountName={0}

 

 

make sure after editing this file to reload the LDAP integration

 

ldap.ovpl -reload

All the best .
Regards
Mostafa Hassan
HP AIS NNM-NA-OO
CCNA-CCNP-ITIL-VCA-Cloud-VCA DataCenter
Highlighted
TMS
Member
Solution

Re: NNM LDAP Integration | Not logging in

Thanks Mostafa

 

The issue was the login name , while BSM accepted the one with alias , NNM accepted one with Full name with space inbetween.  It was pure trial and error . 

 

Issue is solved . 

//Add this to "OnDomLoad" event