Quantcast
Channel: Ignite Realtime : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 10742

Users can't login on a fresh and default openfire install

$
0
0

This is not my first openfire install but this time, I'm completely stuck. I've installed openfire on a (virtual) server running ubuntu and even in with the most simple setup, I'm not able to log in from any client.

 

Some installation details:

 

- version:     openfire 3.7.1, running on JVM 1.6.0_26

- domain:     example.com (ok, that's not the real name, we just use it for now)

- subdomain:  openfire

- apache proxy configuration to redirect "http://openfire.example.com/" to "http://localhost:9090/" (no problem, I can set up the server and log into the admin console)

- embedded database

- servername: "openfire"  (tried "openfire.example.com" as well, no change)

- iptables allows port 5222 (but there's no difference if iptables is running or stopped - no firewall issue)

- openfire is listening to all network interfaces (see openfire.xml)

 

Now, when I try to login as "admin" (or any other user), Spark responds with an "invalid user name or password" message.

 

The credentials I provide with spark are:

 

username:     admin

password:      *******  ;-)

server:          example.com

 

(username "admin@openfire" or "admin@openfire.example.com" makes no difference)

 

Yesterday, I saw from sparks debug console, that there is a message flow between spark and openfire. I see a response from the server. So I doubt right now, that this is some sort of network configuration issue. (Today, after a restart of the clients netbook, spark won't spawn th debug console anymore...)

 

In addition, I can't register new users from the client, even though it is allowed from the openfire setup.

 

 

I'm interested in "the solution" to my problem (of course I am!) and/or some tips on how to debug this problem. The logs didn't help so far, even when I set logging to debug level.

 

TIA!

Andreas

 

---

 

Update - now, that sparks debug console is co-operative again: this is what I see when I try to connect with spark

 

Sent Message(s):

 

<stream:stream to="example.com" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

<starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

<stream:stream to="example.com" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0">

<auth mechanism="PLAIN" xmlns="urn:ietf:params:xml:ns:xmpp-sasl">YWRtaW4AYWRtaW4AbWhiLGx0MW0=</auth>

 

Received Message(s):

<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='1394712306' from='example.com' version='1.0' xml:lang='en'>

<stream:features><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism></mechanis ms></stream:features>

<proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>

<?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='3698008778' from='example.com' version='1.0' xml:lang='en'>

<stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism></mechanis ms></stream:features>

<failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/></failure>


Viewing all articles
Browse latest Browse all 10742

Trending Articles