Using Jabber Messenger to connect to Openfire 3.5.2

Openfire Openfire Support
1

We currently have a JabberNow appliance (JabberNow: 1.1.0.28, Jabber XCP: 4.2) using Jabber Messenger (3.2.1.9). The appliance is lacking to say the least. We are currently testing Openfire 3.5.2 to replace it. We currently have the client deployed on 300+ machine and would like to keep using it if we could.

The problem is, the client cannot log into the Openfire server. All I ever get is, “An unknown error occured.”. Using Spark to connect w/o using auto discover host and port. The logs aren’t showing much, if any information as to the connection issue. Has anyone else tried to use Jabber Messenger to connect to Openfire?

Thanks.

2

Hi tssns,

I’m a bit surprised that you can’t login to an Openfire server using Jabber Messenger. Unfortunately Jabber Messenger isn’t freely available so testing with it is difficult.

When you say the logs aren’t showing much are you referring to the server or client logs? What are your security settings set to in Openfire (Admin Console -> Server -> Server Settings -> Security Settings)? Out of curiosity, are you able to login the JabberNow appliance using Spark?

Cheers,

Ryan

3

Hi ryang,

None of the Openfire logs report anything when I try to connect. But, here is what comes through in the JabberMessenger log:

2008-06-18 13:18:34,232 ERROR com.jabber.jinx.core.prefs.PrefsFace$1$1GlobalPrefsFace - Prefs exception thrown trying to get prefs for id: auth/confirm-password, scope: profile

com.jabber.jinx.core.prefs.JinxPrefsException: Preference does not exist: auth/confirm-password

2008-06-18 13:18:34,232 ERROR com.jabber.jinx.core.prefs.PrefsFace$1$1GlobalPrefsFace - Prefs exception thrown trying to get prefs for id: auth/confirm-password, scope: profile

com.jabber.jinx.core.prefs.JinxPrefsException: Preference does not exist: auth/confirm-password

2008-06-18 13:18:46,685 ERROR com.jabber.sdk.ssl.NativeX509TrustManager - No root certs found for issuer ‘CN=steved.tss’. Returning false.

2008-06-18 13:18:46,685 ERROR com.jabber.sdk.ssl.NativeX509TrustManager - Cert signature cannot be verified. Chain is not valid. Returning false.

2008-06-18 13:18:46,982 ERROR com.jabber.sdk.sasl.JMSASLFeatureConsumer - Unable to create SaslClient. Failure either in authentication or could not find a matching mechanism.

2008-06-18 13:18:47,029 ERROR com.jabber.sdk.sasl.JMSASLFeatureConsumer - Could not create SaslClient.

org.jabberstudio.jso.sasl.NoSupportedMechanismsException: Unable to create SaslClient. Failure either in authentication or could not find a matching mechanism.

at com.jabber.sdk.sasl.JMSASLFeatureConsumer.startConsumption(JMSASLFeatureConsume r.java:282)

at org.jabberstudio.jso.features.AbstractFeatureConsumer.consume(AbstractFeatureCo nsumer.java:91)

at org.jabberstudio.jso.features.FeaturesetConsumerManager.process(FeaturesetConsu merManager.java:547)

at com.jabber.sdk.session.JMFeaturesetConsumerManager.process(JMFeaturesetConsumer Manager.java:72)

at org.jabberstudio.jso.features.FeaturesetConsumerManager$Context.featuresReporte d(FeaturesetConsumerManager.java:147)

at net.outer_planes.jso.AbstractStream.fireFeaturesReported(AbstractStream.java:70 2)

at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(AbstractStream.j ava:626)

at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1081)

at org.jabberstudio.jso.features.FeaturesetConsumerManager.run(FeaturesetConsumerM anager.java:571)

at com.jabber.sdk.session.XMPPAuthStrategy.performAuth(XMPPAuthStrategy.java:121)

at com.jabber.sdk.session.SessionComponent.login(SessionComponent.java:1137)

at com.jabber.jinx.session.JinxSessionComponent.handleLogin(JinxSessionComponent.j ava:681)

at com.jabber.jinx.session.JinxSessionComponent$13.clientPacketMatched(JinxSession Component.java:1024)

at com.jabber.sdk.clientpacket.ClientPacketListener.clientPacketMatched(ClientPack etListener.java:353)

at com.jabber.sdk.clientpacket.ClientPacketListener.packetMatched(ClientPacketList ener.java:239)

at com.jabber.sdk.clientpacket.ClientPacketListener.packetTransferred(ClientPacket Listener.java:264)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientPacketQueue.firePacketTransfer redReceivedEvent(ClientPacketQueue.java:338)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientPacketQueue.performProcessPost (ClientPacketQueue.java:154)

at org.jabberstudio.jso.util.QueuedPacketRouter.process(QueuedPacketRouter.java:56 2)

at com.jabber.sdk.clientpacket.dispatchrouter.ActionDispatcher.processHandlers(Act ionDispatcher.java:94)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter$KeyDispatcher.p rocessHandlers(ClientDispatchRouter.java:248)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.processHandlers (ClientDispatchRouter.java:403)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.process(ClientD ispatchRouter.java:503)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.send(ClientDisp atchRouter.java:475)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.send(ClientDisp atchRouter.java:453)

at org.jabberstudio.jso.util.Monitor$MonitorTask.send(Monitor.java:236)

at org.jabberstudio.jso.util.Monitor.sendAndWatch(Monitor.java:750)

at org.jabberstudio.jso.util.PacketMonitor.sendAndWatch(PacketMonitor.java:425)

at org.jabberstudio.jso.util.PacketMonitor.sendAndWatch(PacketMonitor.java:367)

at com.jabber.sdk.clientpacket.ClientPacketWatcher.sendAndWatch(ClientPacketWatche r.java:56)

at com.jabber.sdk.clientpacket.ClientPacketHelper.sendAndWatch(ClientPacketHelper. java:74)

at com.jabber.sdk.clientpacket.ClientPacketHelper.sendAndWatch(ClientPacketHelper. java:89)

at com.jabber.jinx.login.LoginFace$LoginRunner.run(LoginFace.java:78)

at java.lang.Thread.run(Unknown Source)

2008-06-18 13:18:47,044 ERROR com.jabber.jinx.offline.JinxOfflineComponent - closeHistory(): There was no IHistory object to detach.

2008-06-18 13:18:47,044 ERROR com.jabber.jinx.broadcast.JinxBroadcastComponent - closeHistory(): There was no IHistory object to detach.

2008-06-18 13:18:47,060 ERROR com.jabber.jinx.session.JinxSessionComponent - error

org.jabberstudio.jso.util.PacketException

at com.jabber.sdk.session.XMPPAuthStrategy.performAuth(XMPPAuthStrategy.java:133)

at com.jabber.sdk.session.SessionComponent.login(SessionComponent.java:1137)

at com.jabber.jinx.session.JinxSessionComponent.handleLogin(JinxSessionComponent.j ava:681)

at com.jabber.jinx.session.JinxSessionComponent$13.clientPacketMatched(JinxSession Component.java:1024)

at com.jabber.sdk.clientpacket.ClientPacketListener.clientPacketMatched(ClientPack etListener.java:353)

at com.jabber.sdk.clientpacket.ClientPacketListener.packetMatched(ClientPacketList ener.java:239)

at com.jabber.sdk.clientpacket.ClientPacketListener.packetTransferred(ClientPacket Listener.java:264)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientPacketQueue.firePacketTransfer redReceivedEvent(ClientPacketQueue.java:338)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientPacketQueue.performProcessPost (ClientPacketQueue.java:154)

at org.jabberstudio.jso.util.QueuedPacketRouter.process(QueuedPacketRouter.java:56 2)

at com.jabber.sdk.clientpacket.dispatchrouter.ActionDispatcher.processHandlers(Act ionDispatcher.java:94)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter$KeyDispatcher.p rocessHandlers(ClientDispatchRouter.java:248)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.processHandlers (ClientDispatchRouter.java:403)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.process(ClientD ispatchRouter.java:503)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.send(ClientDisp atchRouter.java:475)

at com.jabber.sdk.clientpacket.dispatchrouter.ClientDispatchRouter.send(ClientDisp atchRouter.java:453)

at org.jabberstudio.jso.util.Monitor$MonitorTask.send(Monitor.java:236)

at org.jabberstudio.jso.util.Monitor.sendAndWatch(Monitor.java:750)

at org.jabberstudio.jso.util.PacketMonitor.sendAndWatch(PacketMonitor.java:425)

at org.jabberstudio.jso.util.PacketMonitor.sendAndWatch(PacketMonitor.java:367)

at com.jabber.sdk.clientpacket.ClientPacketWatcher.sendAndWatch(ClientPacketWatche r.java:56)

at com.jabber.sdk.clientpacket.ClientPacketHelper.sendAndWatch(ClientPacketHelper. java:74)

at com.jabber.sdk.clientpacket.ClientPacketHelper.sendAndWatch(ClientPacketHelper. java:89)

at com.jabber.jinx.login.LoginFace$LoginRunner.run(LoginFace.java:78)

at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.IllegalStateException: org.jabberstudio.jso.sasl.NoSupportedMechanismsException: Unable to create SaslClient. Failure either in authentication or could not find a matching mechanism.

at com.jabber.sdk.sasl.JMSASLFeatureConsumer.startConsumption(JMSASLFeatureConsume r.java:293)

at org.jabberstudio.jso.features.AbstractFeatureConsumer.consume(AbstractFeatureCo nsumer.java:91)

at org.jabberstudio.jso.features.FeaturesetConsumerManager.process(FeaturesetConsu merManager.java:547)

at com.jabber.sdk.session.JMFeaturesetConsumerManager.process(JMFeaturesetConsumer Manager.java:72)

at org.jabberstudio.jso.features.FeaturesetConsumerManager$Context.featuresReporte d(FeaturesetConsumerManager.java:147)

at net.outer_planes.jso.AbstractStream.fireFeaturesReported(AbstractStream.java:70 2)

at net.outer_planes.jso.AbstractStream.firePacketTransferredEvent(AbstractStream.j ava:626)

at net.outer_planes.jso.AbstractStream.process(AbstractStream.java:1081)

at org.jabberstudio.jso.features.FeaturesetConsumerManager.run(FeaturesetConsumerM anager.java:571)

at com.jabber.sdk.session.XMPPAuthStrategy.performAuth(XMPPAuthStrategy.java:121)

… 24 more

Caused by: org.jabberstudio.jso.sasl.NoSupportedMechanismsException: Unable to create SaslClient. Failure either in authentication or could not find a matching mechanism.

at com.jabber.sdk.sasl.JMSASLFeatureConsumer.startConsumption(JMSASLFeatureConsume r.java:282)

… 33 more

The security for Openfire is set to “Optional” for client and server. Also, I don’t have any problems trying to connect to the JabberNow server using Spark. It’s really odd.

4

Hi tssns,

It’s hard to know if this is the root problem but looking at those error messages it looks like the Jabber Messenger doesn’t like the security certificate in Openfire. Did you add a certificate to Openfire?

Thanks,

Ryan

5

Ryan,

I have the initial certs that are created during the install process. I removed those and tried to reconnect not using ssl but, still no luck. I also recreated the certs and tried to connect again but, I’m still getting the “an unknown error occurred”.

Thanks,

Steve

6

Hi Steve,

The certificate idea was just a shot in the dark. It might still be a/the issue but it’s difficult to tell. I know you didn’t want to deploy new clients but it looks like that version of Jabber Messenger is a little old so upgrading to a newer client might not be a bad idea.

Thanks,

Ryan

7

Ryan,

An email came through a little bit ago for their new version of MomentIM. On a whim I decided to give the client a try. I downloaded it, got it installed, and it connected without any problems at all. I logged into our Jabber account but, the only client available to us is 3.2.1.9, which is what I’ve been using to test with. Is there a newer version available?

Thanks,

Steve

8

Steve,

I was under the impression that the MomentIM client was just the newest version/name of the JabberMessnger client but I could be mistaken. It’s been a number of years since I’ve used the XCP server and the associated client so my knowledge of their products is a bit lacking.

When you say that MomentIM connected without any problems was that to Openfire or their (IM) appliance?

Thanks,

Ryan

9

Ryan,

It was Openfire that I connected to. I’m not sure if the MomentIM product is their new client or not. It seems pretty much the same as JabberMessenger. It looks like we may end up deploying Spark as the new client to go along with Openfire. The JabberNow appliance is just way too limiting in regards to functionality and administrative tasks. Thanks for all the help.

Steve.