[OPEN-ILS-DEV] Jabber authentication error

[Mike Rylander]

On 6/18/07, Sperr, Edwin <sperr at nelinet.net> wrote:
> I've gone through the process of building Release 1.1.5 on a new Ubuntu
> install.  All seems to be well except for the fact that there seems to
> be some sort of authentication hiccup with jabber on start-up.  To wit,
> I get...
>
>
[snip]
>
>   * ! EXCEPTION ! *
> TYPE: OpenSRF::EX::Jabber
> Mess: Jabber Exception
> Mess:  *
> evergreen at localhost/system_client_drone_at_eg-server.nelinet.lan: Unable
> to authenticate: <iq type='error' id='123'>
> Mess: <query xmlns='jabber:iq:auth'>
> Mess: <username>[myusername]</username>
> Mess: <password>[mypassword]</password>
> Mess:
> <resource>system_client_drone_at_eg-server.nelinet.lan_7371</resource>
> Mess: </query>
> Mess: <error code='401' type='auth'><not-authorized
> xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
> Loc.: 535 OpenSRF::Transport::SlimJabber::Client
> Loc.: /openils/lib/perl5/OpenSRF/Transport/SlimJabber/Client.pm
> Time: Mon Jun 18 11:38:46 2007
> Starting OpenSRF C (host=eg-server.nelinet.lan)
>

I notice here that Evergreen thinks the machine is called
eg-server.nelinet.lan, but the jabber client is attempting to connect
to localhost (evergreen at localhost/system_client_drone_at_eg-server.nelinet.lan).

Are you registering the user via the loopback (localhost) address
(evergreen at localhost) or against the "real" interface
(evergreen at eg-server.nelinet.lan)?  If the latter, please try
registering via the former (localhost) as well.  Or you can tell
Evergreen to use the machine's name as the Jabber domain in
bootstrap.conf and opensrf_core.xml.

Let us know if that helps!

--miker