Project:XMPP Framework
Version:6.x-6.x-dev
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

I tried playing around with the XMPP framework months back and again in the recent days. I am trying to understand and come to a conclusion as to if the framework is able to support communications to an Openfire server. I see mention of ejabberd in the setup, but nothing about other popular XMPP/Jabber solutions such as Openfire. My end goal with this is to have chatting capabilities within the site hopefully using the xmppframework as the middle man to get to the backend Openfire server. Do you guys have any thoughts or comments on this?

Comments

#1

OpenFire support is going to be tested, it did work with OpenFire previously so i guess something has altered in OpenFires implementation of the http-bind protocol.
Will be verifying in the coming weeks when time permits.

#2

Subscribing

#3

I just set up an openfire server 3.6.4 and the xwchat client connected to the openfire server first time without any changes to it on the http-bind interface the same as the ejabberd server did.

If you guys are using openfire make sure your apache re-direct is going directly too openfires http bind port 7070 and the /http-bind/ is added to the end of this otherwise you wont be able to log in.

#4

subscribe

#5

Status:active» closed (fixed)

Closing since OpenFire is working with the XWChat and all known sub modules with the pure xmpp api enabled.

#6

Here is my documentation if anyone stumbles upon this...

http://www.dueyesterday.net/node/36

#7

Status:closed (fixed)» active

Is the redirect in Apache necessary also when Apache and Openfire are located on the same server?

I'm trying to follow the tutorial from #6 with authentication against the Drupal DB instead of an LDAP server.

Hitting mysite/http-bind gives me a 404, not a 400 (per the guide), so I guess I haven't configured it correctly.

I also have a hard time storing JIDs for the users, as the module will not accept user@localhost for local testing, probably demands another domain name.