Fedora Core 4, jabberd-2.0-0.s11.9.fc4: pam auth failure

Hi all,

I've just installed jabberd-2.0-0.s11.9.fc4 from the Fedora
Extras 
repository via yum on Fedora Core 4. It's set up to use pam
as the auth 
module and berkeley DB as the storage module (as per the RPM
defaults), 
and I've configured /etc/jabberd/c2s.xml and
/etc/jabberd/sm.xml with 
<id> as the name of the server (which resolves
properly in DNS).

Each time I try to connect to the server as users that exist
on the 
server (and can log in via ssh and dovecot imap), I get the
following 
line in /var/log/messages:

Mar 15 14:18:21 tungsten jabberd(pam_unix)[18805]:
authentication 
failure; logname= uid=100 euid=100 tty= ruser= rhost= 
user=ben
Mar 15 14:18:41 tungsten jabberd(pam_unix)[18805]:
authentication 
failure; logname= uid=100 euid=100 tty= ruser= rhost= 
user=glenr

my /etc/pam.d/jabberd looks like this:

#%PAM-1.0
auth       required     pam_nologin.so
auth       required     pam_stack.so service=system-auth
account    required     pam_stack.so service=system-auth
session    required     pam_stack.so service=system-auth

(Which is, for comparison, the same as /etc/pam.d/dovecot.)

I've googled and can't find anything useful. Has anyone seen
this 
problem and/or can help fix it?

Thanks,

  - Ben

-- 
"If you made a Venn diagram [of my life], there would
be two 
non-overlapping circles, one of which was labeled, 'Times
when I am 
truly happy' and the other of which was labeled, 'Times when
I am logged 
in as root, holding a cable, or have the case open.' "
  - Jamie Zawinski [jwz.org]
_______________________________________________
JAdmin mailing list
JAdminjabber.org
http:/
/mail.jabber.org/mailman/listinfo/jadmin
FAQ: http://ww
w.jabber.org/about/jadminfaq.shtml
_______________________________________________

Hi again,

Just after posting this (of course), I managed to fix it.
For the 
benefit of anyone else who comes across the same problem:

It turned out that jabber was requesting the password for
the same uid 
every time (100, rather than the right ones which are both
> 500). I 
made /etc/shadow readable to the jabber user, and it's now
working.

  - Ben

-- 
"If you made a Venn diagram [of my life], there would
be two 
non-overlapping circles, one of which was labeled, 'Times
when I am 
truly happy' and the other of which was labeled, 'Times when
I am logged 
in as root, holding a cable, or have the case open.' "
  - Jamie Zawinski [jwz.org]

On 15/03/2007 2:29 PM, Ben Williams wrote:
> Hi all,
> 
> I've just installed jabberd-2.0-0.s11.9.fc4 from the
Fedora Extras 
> repository via yum on Fedora Core 4. It's set up to use
pam as the auth 
> module and berkeley DB as the storage module (as per
the RPM defaults), 
> and I've configured /etc/jabberd/c2s.xml and
/etc/jabberd/sm.xml with 
> <id> as the name of the server (which resolves
properly in DNS).
> 
> Each time I try to connect to the server as users that
exist on the 
> server (and can log in via ssh and dovecot imap), I get
the following 
> line in /var/log/messages:
> 
> Mar 15 14:18:21 tungsten jabberd(pam_unix)[18805]:
authentication 
> failure; logname= uid=100 euid=100 tty= ruser= rhost= 
user=ben
> Mar 15 14:18:41 tungsten jabberd(pam_unix)[18805]:
authentication 
> failure; logname= uid=100 euid=100 tty= ruser= rhost= 
user=glenr
> 
> my /etc/pam.d/jabberd looks like this:
> 
> #%PAM-1.0
> auth       required     pam_nologin.so
> auth       required     pam_stack.so
service=system-auth
> account    required     pam_stack.so
service=system-auth
> session    required     pam_stack.so
service=system-auth
> 
> (Which is, for comparison, the same as
/etc/pam.d/dovecot.)
> 
> I've googled and can't find anything useful. Has anyone
seen this 
> problem and/or can help fix it?
> 
> Thanks,
> 
>  - Ben
> 
_______________________________________________
JAdmin mailing list
JAdminjabber.org
http:/
/mail.jabber.org/mailman/listinfo/jadmin
FAQ: http://ww
w.jabber.org/about/jadminfaq.shtml
_______________________________________________