Admin interface has no bearing on server instance

Shiraz · October 11, 2007, 10:20pm

Hi all,

I installed a fresh Openfire, created a mySQL database, logged into the admin interface, ran through setup successfully, then logged into the admin screen and created a user.
I could not connect to the server from my jabber client as the user I created via the admin interface, but I could connect if I told my client to create the user on the server, and was able to have a successful chat.
I checked the users/groups tab in the admin interface. My original user was there, but not the one created by the client.
I checked the sessions tab in the admin interface. The active session of my client was not in the sessions tab.
Changed the setting via the admin interface to disallow client creation of new accounts, restarted server, but was still able to create a new account via my client.

So essentially it appears that the admin interface settings have no relation or bearing to the actual operation of the sever.

Are there multiple conf files or something?

I thought maybe it was a database problem so I re-setup the admin, this time using the embedded database. Same problem.

I’m sure it’s something obvious, but I haven’t found the answer to this after some time! Help is greatly appreciated!

Thank you,

Shiraz

Gaston_Dombiak · October 12, 2007, 3:51am

Hey Shiraz,

Are you sure you are connecting to your Openfire instance from your client?

Open the XML console window from your client and post the XML that you are sending and receiving. Also log into the admin console and post here the domain of your server that you see in that page.

Regards,

– Gato

Shiraz · October 12, 2007, 7:24am

I think you’ve got me on the right track here.

A) from the admin interface:

Server Name:

devel.affinitybridge.com

B) Client (Spark) console when trying to connect to the server:

For the account that does not work, which iscreated on the above-mentioned server:

Raw sent packets:

<stream:stream to=“devel.affinitybridge.com” xmlns=“jabber:client” xmlns:stream=“http://etherx.jabber.org/streams” version=“1.0”>

<iq id=“6UClw-0” type=“get”><query xmlns=“jabber:iq:auth”><username>shiraz</username></query> </iq>

Raw received packets:

<?xml version=‘1.0’?><stream:stream xmlns:stream=‘http://etherx.jabber.org/streams’ id=‘470F1B4A’ xmlns=‘jabber:client’ from=‘devel.affinitybridge.com’>

<iq id=‘6UClw-0’ type=‘error’><query xmlns=‘jabber:iq:auth’><username>shiraz</username></query> <error code=‘401’>Unauthorized</error></iq>

For the account that does work, which is not created on the server, but for which I used the client to succesfully create the account and subsequently log in:

Raw sent packets:

<stream:stream to=“devel.affinitybridge.com” xmlns=“jabber:client” xmlns:stream=“http://etherx.jabber.org/streams” version=“1.0”>

<iq id=“6UClw-1” type=“get”><query xmlns=“jabber:iq:auth”><username>shiraz2</username></query&gt ;</iq>

<iq id=“6UClw-2” type=“set”><query xmlns=“jabber:iq:auth”><username>shiraz2</username><digest&gt ;14ed88571b3cbbc7ac75364d3ea934065960a6e6</digest><resource>spark&lt ;/resource></query></iq>

</iq>

<presence id=“6UClw-7”><status>Available</status><priority>1</pri ority></presence>

Raw received packets:

<?xml version=‘1.0’?><stream:stream xmlns:stream=‘http://etherx.jabber.org/streams’ id=‘470F1C99’ xmlns=‘jabber:client’ from=‘devel.affinitybridge.com’>

<iq id=‘6UClw-1’ type=‘result’><query xmlns=‘jabber:iq:auth’><username>shiraz2</username><digest/&g t;<password/><resource/></query></iq>

</iq>

<iq id=‘6UClw-11’ to=‘shiraz2@devel.affinitybridge.com/spark’ type=‘result’ from=‘devel.affinitybridge.com’><query xmlns=‘http://jabber.org/protocol/disco#items’><item jid=‘users.jabber.org’ name=‘Jabber User Directory’/></query></iq><iq id=‘6UClw-9’ to=‘shiraz2@devel.affinitybridge.com/spark’ type=‘error’ from=‘users.jabber.org’><query xmlns=‘http://jabber.org/protocol/disco#info’/><error code=‘502’>Server Connect Failed</error></iq>

<iq id=‘6UClw-12’ to=‘shiraz2@devel.affinitybridge.com/spark’ type=‘error’ from=‘users.jabber.org’><query xmlns=‘http://jabber.org/protocol/disco#info’/><error code=‘502’>Server Connect Failed</error></iq>

<iq id=‘6UClw-15’ to=‘shiraz2@devel.affinitybridge.com/spark’ type=‘error’ from=‘users.jabber.org’><query xmlns=‘http://jabber.org/protocol/disco#info’/><error code=‘502’>Server Connect Failed</error></iq>

So it seems that the working account (shiraz2) is actually authenticating against a public jabber server, which explains the discrepency. Now why on earth that’s happening, I can’t understand. The client is configured to use the affinity server. In fact, in a separate information tab, it does say that the host is the affinity server under ‘connection information’.

Note also the “server connect failed” in the received packets in the working account (shiraz2).

I wish I knew the XMPP protocol better (ie. at all!).

I have a feeling this might be what you need to figure out something obvious. But really, what more is there to configure? The client setup is obvious and simple, and in fact I’m having the exact same problem with another Jabber client (by the same company), Pidgin (ie. Gaim).

Thanks Gato (and anyone else who might step in (wink wink nudge nudge),

Shiraz

Shiraz · October 24, 2007, 6:36pm

This issue seems to have resolved itself. Go figure.