LDAP + ssl

I’‘ve been able to get 2.1.1 to work against my openldap server pretty well. But, I’'m having problems getting it to hit the ssl port. My ldap part of the config is ::

myserver.mydomain.com

636

uid

cn

mail

ou=people,dc=mydomain,dc=com

True

org.jivesoftware.messenger.ldap.LdapUserProvider

org.jivesoftware.messenger.ldap.LdapAuthProvider

But, when running tcpdump port 636… I don’‘t see any traffic. Nor do I see any errors in the logs. I’‘ve been able to auth a linux workstation against port 636 w/ ssl against the ldap server… so I’'m pretty confident that side of the equation is working. Thanks.

-jason

Getting a little further… here’'s some debugging info…

2005.02.17 14:56:00 Logging off client.mydomain.com/660442f8 on org.jivesoftware.messenger.net.SocketConnection@9300cc

2005.02.17 14:56:05 Connect Socket[addr=/192.168.19.77,port=37293,localport=5222]

2005.02.17 14:56:05 Trying to find a user’'s DN based on their username. uid: rohwedde, Base DN: ou=people,dc=mydomain,dc=com…

2005.02.17 14:56:05 Creating a DirContext in LdapManager.getContext()…

2005.02.17 14:56:05 Created hashtable with context values, attempting to create context…

2005.02.17 14:56:05 Exception thrown when searching for userDN based on username ‘‘rohwedde’’

javax.naming.CommunicationException: server.mydomain.com:636 [Root exception is java.lang.ClassNotFoundException: com.jivesoftware.util.ssl.DummySSL

SocketFactory]

at com.sun.jndi.ldap.Connection.(Connection.java:204)

at com.sun.jndi.ldap.LdapClient.(LdapClient.java:118)

at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1578)

at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2596)

at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:283)

at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)

at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)

at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)

at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)

at javax.naming.InitialContext.init(InitialContext.java:223)

at javax.naming.ldap.InitialLdapContext.(InitialLdapContext.java:134)

at org.jivesoftware.messenger.ldap.LdapManager.getContext(LdapManager.java:216)

at org.jivesoftware.messenger.ldap.LdapManager.findUserDN(LdapManager.java:379)

at org.jivesoftware.messenger.ldap.LdapManager.findUserDN(LdapManager.java:334)

at org.jivesoftware.messenger.ldap.LdapAuthProvider.authenticate(LdapAuthProvider. java:88)

at org.jivesoftware.messenger.auth.AuthFactory.authenticate(AuthFactory.java:100)

at org.jivesoftware.messenger.handler.IQAuthHandler.login(IQAuthHandler.java:180)

at org.jivesoftware.messenger.handler.IQAuthHandler.handleIQ(IQAuthHandler.java:12 2)

at org.jivesoftware.messenger.handler.IQHandler.process(IQHandler.java:48)

at org.jivesoftware.messenger.IQRouter.handle(IQRouter.java:192)

at org.jivesoftware.messenger.IQRouter.route(IQRouter.java:74)

at org.jivesoftware.messenger.PacketRouter.route(PacketRouter.java:78)

at org.jivesoftware.messenger.net.SocketReadThread.readStream(SocketReadThread.jav a:207)

at org.jivesoftware.messenger.net.SocketReadThread.run(SocketReadThread.java:109)

Caused by: java.lang.ClassNotFoundException: com.jivesoftware.util.ssl.DummySSLSocketFactory

at java.net.URLClassLoader$1.run(URLClassLoader.java:200)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:188)

at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

at java.lang.ClassLoader.loadClass(ClassLoader.java:251)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:242)

at com.sun.jndi.ldap.VersionHelper12.loadClass(VersionHelper12.java:32)

at com.sun.jndi.ldap.Connection.createSocket(Connection.java:264)

at com.sun.jndi.ldap.Connection.(Connection.java:181)

… 25 more

rohwedde,

It looks like this bug was already fixed (JM-152) and will be coming out with the next release of Jive Messenger. You could download a nightly build until the release if you need the fix urgently.

Regards,

Matt