Hi,
I need some help urgnelty.. as no idea why its acting funy.
as far I belive, I have setup ldap server properly in test
environment, but actiting wired.. no idea why ...
example
[root@test ~]# id tuser
id: tuser: No such user
bellow command shows the correct info :
[root@test ~]#
-D 'cn=Directory Manager'
It looks like your ldapsearch is using Directory Manager (the 389 equivalent to
the root user). However I do not see where you have specified a bind DN in an
ldap.conf file so possibly PAM is binding anonymously and an ACL is prohibiting
the search?
If this is a
Hi
Thanks for the quick Reply. I was thinking that same that some where
its missing the Bind dn
and I can conferm that, its working with definning
binddn and bindpw in ldap.conf
but ,
I confiered this before and I never had to define binddn and bindpw
in any where in ldap.conf and as you said
Hi
Thanks for the quick Reply. I was thinking that same that some where
its missing the Bind dn
and I can conferm that, its working with definning
binddn and bindpw in ldap.conf
but ,
I confiered this before and I never had to define binddn and bindpw
in any where in ldap.conf and as you said
On Sun, Dec 29, 2013 at 05:33:09PM +, fosiul alam wrote:
Hi
Thanks for the quick Reply. I was thinking that same that some where
its missing the Bind dn
and I can conferm that, its working with definning
binddn and bindpw in ldap.conf
but ,
I confiered this before and I never had
