hi,
I’'ve installed wildfire and users came from an LDAP server ,fedora directory server.Wildfire asked me to set one of them as the wildfire admin,and i did so.
Now,when i’'m using jeti to connect to the server,only this admin can login correctly.The other users are recognized by wildfire,but their password are refused.
May you explain me what is the problem and how i can resolve it?
Thanks.
Hi,
it may help a lot if you enable ldap.debug and post here what’'s going wrong. Also your LDAP settings in wildfire.xml may be interesting, you may want to remove all sensitive information.
LG
Here is my wildfire.xml file: (i don’'t modify it after setup)
]]>
cn
cn
member
description
false
org.jivesoftware.wildfire.ldap.LdapVCardProvider
org.jivesoftware.wildfire.ldap.LdapUserProvider
org.jivesoftware.wildfire.ldap.LdapAuthProvider
org.jivesoftware.wildfire.ldap.LdapGroupProvider
true
true
ssName>org.jivesoftware.wildfire.ldap.LdapAuthProvider
org.jivesoftware.wildfire.ldap.LdapGroupProvider
org.jivesoftware.wildfire.ldap.LdapAuthProvider
org.jivesoftware.wildfire.ldap.LdapGroupProvider
true
ssName>org.jivesoftware.wildfire.ldap.LdapAuthProvider
Hi,
one thing I wonder about is your “” to be a DN.
LG
hi,
I’'ve changed the admin dn to uid=adminexample,ou=Special Users,dc=example,dc=org.
But my problem isn’'t resolved yet.
Other details:When i try to open a session with the jaber client exodus,it follows two steps:First it connects to the server with the provided username.This step walks for any user stored in the ldap directory.secondly,exodus tries to authenticate this user. It is at this level that the connection is broken.And exodus sends an error message to notify that either the password is wrong (of course, i’'ve typed the right pass),either the user is already connected (which is false). owever the admin user (adminexample) can open a session without any problem.
Maybe you’'ve already meet these problems?
Thanks for your help.
Hi,
as I said before it may help a lot if you enable ldap.debug and post here what’'s going wrong. It could be the wrong search base or something like this.
Lg
hi,
here is the ldap debug :
+*2006.12.10 20:24:38 Connect Socket[addr=/192.168.0.124,port=1650,localport=5222]
2006.12.10 20:25:23 Trying to find a user’'s DN based on their username. uid: pattchen, Base DN: dc=example,dc=org…
2006.12.10 20:25:23 Creating a DirContext in LdapManager.getContext()…
2006.12.10 20:25:23 Created hashtable with context values, attempting to create context…
2006.12.10 20:25:23 … context created successfully, returning.
2006.12.10 20:25:23 Starting LDAP search…
2006.12.10 20:25:23 … search finished
2006.12.10 20:25:23 In LdapManager.checkAuthentication(userDN, password), userDN is: uid=“pattchen”,ou=“GenieInformatique”,ou=“Eleves”…
2006.12.10 20:25:23 Created context values, attempting to create context…
2006.12.10 20:25:23 Caught a naming exception when creating InitialContext
javax.naming.AuthenticationException: LDAP: error code 49 - Invalid Credentials
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.connect(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.
2006.12.10 20:25:54 Trying to find a user’'s DN based on their username. uid: adminexample, Base DN: dc=example,dc=org…
2006.12.10 20:25:54 Creating a DirContext in LdapManager.getContext()…
2006.12.10 20:25:54 Created hashtable with context values, attempting to create context…
2006.12.10 20:25:54 … context created successfully, returning.
2006.12.10 20:25:54 Starting LDAP search…
2006.12.10 20:25:54 … search finished
2006.12.10 20:25:54 In LdapManager.checkAuthentication(userDN, password), userDN is: uid=“adminexample”,ou=“Special Users”…
2006.12.10 20:25:54 Created context values, attempting to create context…
2006.12.10 20:25:54 … context created successfully, returning.*+
As you have certainly noticed,the user pattchen cannot connect while the admin doesn’'t have problems.
Pat Tchen.