I’'ve been trying to setup Jive Messenger 2.3.0 beta 1 to authenticate against PAM on a RHEL3 machine without luck.
I added the corresponding provider sections and defined the nativeAuth domain to ‘‘shaj’’, created the ``
file with the following contents, as read in the shaj documentation:
auth required pam_stack.so service=system_auth
The authentication will always fail and the PAM subsystem will log this:
Nov 3 14:32:32 celonia shaj(pam_unix): authentication failure; logname= uid=508 euid=508 tty= ruser= rhost= user=peralta
Other services on the same machine authenticate against local accounts using PAM without problems.
I modified the ``
file to allow every login:
auth sufficient pam_permit.so #auth required pam_stack.so service=system_auth
And it worked. I also tried avoiding ``
entirely and using ``
directly with no luck. I am wondering with the user password supplied by the Jabber client (sent in plaintext) is reaching the pam subsystem.