ejabberd - Comments for "[SOLVED] Unable to authenticate with pam on 16.04"

Quote: I found out that on my

holger — Wed, 14 Sep 2016 09:05:11 +0000

Quote:

I found out that on my Gentoo install there are 2 copies of epam

This sounds like a Gentoo packaging issue.

Aha thanks! I've been banging

techiem2 — Tue, 13 Sep 2016 21:44:01 +0000

Aha thanks!
I've been banging my head on this since I upgraded last night.
I found out that on my Gentoo install there are 2 copies of epam and apparently ejabberd uses both for different things. I had already fixed the one in the ejabberd directory (which resolved several errors), but not the other one you mentioned (which fixed actual auth).

I found this Fedora issue

Stormwind — Sat, 27 Aug 2016 20:37:38 +0000

I found this Fedora issue related to ejabberd and epam:
https://bugzilla.redhat.com/show_bug.cgi?id=1337216

And I posted a workaround there - make epam setuid root as the ejabberd instructions enumerate:
chmod 4750 /usr/lib/erlang/lib/p1_pam-1.0.0/priv/bin/epam

I ran into this same issue

Stormwind — Sat, 27 Aug 2016 20:14:39 +0000

I ran into this same issue when upgrading from Fedora 22 to Fedora 24.

Fedora now packages epam in the erlang-p1_pam package, which I have installed - but I can find no instructions on how to configure ejabberd to start epam.

The issue was that epam

joed — Sat, 27 Aug 2016 01:21:00 +0000

The issue was that epam wasn't running as root.

I'd seen that this needed to be done in the documentation, but did not realize that ejabberd starts epam and leaves it running. So when I toggled it initially, it didn't seem to have any effect.

I had to shut down the server, then do the chmod, then restart to get it all to work.