We've had 3 spacewalk users that have upgraded from 1.0 to 1.1 and have the their pam authentication stop working.
In all cases logging in with a pam authenticated user resulted in a java dump (the jvm crashing).
In all 3 cases reverting from the oci driver back to the thin driver fixed the issue. I know Michael has tested this on a spacewalk 1.1 build directly, but since 3 different users had the issue and all 3 reported it working with the thin driver, I think something is awry.
We should test upgrading from 5.3 to 5.4 (or spacewalk 1.0 to 1.1) with pam authentication enabled.
This problem is in fact being worked on in bug #627859.
I'll leave this bug open for QA to properly verify the pam authentication
on upgraded Satellite works OK.
(In reply to comment #0)
> We've had 3 spacewalk users that have upgraded from 1.0 to 1.1 and have the
> their pam authentication stop working.
Could you please confirm that in all these cases, the PAM authentication is in fact using LDAP and not some other PAM module?
We are aware of LDAP having issues but if it is a more generic PAM problem, please let me know.
The bug 627859 is now ON_QA, so this one could be moved ON_QA as well. Or closed as dupe?
This is tracking over /upgrades/ the other is new installs. I think its good to have it track for upgrades to ensure QA specifically tests this, even if we developers feel like were tracking the same issue in two bugs and should be closed as dupe. Lets move to ON_QA once Milan hands QA the rhn-upgrade package.
Verified on Satellite upgraded from 5.3 to 5.4.
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release.
RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade
RHEA-2010:0803 - RHN Tools enhancement update
RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update
RHEA-2010:0800 - RHN Satellite Server 5.4.0
Docs are available: