Description of problem: rhn_register from a RHEL3, RHEL4, or RHEL5 beta2 client going to a RHN Satellite 5.0 beta system fails if the username given at system registration time has PAM authentication enabled. Registration of these succeeds if the username does not have PAM authentication enabled. rhn_register failure on RHEL3 and RHEL4 happens immediately following clicking "Next" on the "Register a User Account" page in the TUI. It looks like: There was an SSL error: (-1, 'Unexpected EOF') A common cause of this error is the system time being incorrect. Verify that the time on this system is correct. rhn_register failure on RHEL5 beta2 happens later, at the point where the package list is sent to the server. The TUI displays: Problem registering login name. The whole point of enabling PAM is to not need local passwords. PAM authentication is working fine on the web GUI, it's only failing for rhn_register. Version-Release number of selected component (if applicable): rhns-xmlrpc-4.9.0-18.rhel4 How reproducible: always
/var/log/debug indicates that the PAM authentication step is succeeding, but for some reason the xmlrpc call is reporting a failure after that. I'm looking...
This failure is impacting Dell's ability to test RHEL5 betas. Please respond ASAP. Everything else about the Satellite Server is working, except the ability to register systems to it when using PAM authentication. The RHEL5 client failure can't print out a good error report either, it tracebacks. [Tue Dec 12 16:28:50 2006] rhn_register Traceback (most recent call last): File "/usr/share/rhn/up2date_client/tui.py", line 1213, in __init__ rhnreg.registerUser(tui.userName, tui.password, tui.email) File "/usr/share/rhn/up2date_client/rhnreg.py", line 222, in registerUser s.registration.new_user(username, password, email) File "/usr/share/rhn/up2date_client/rhnserver.py", line 62, in __call__ message = pieces[2].strip(" '") exceptions.IndexError: list index out of range Stubbing out /usr/share/rhn/server/rhnUser.pm:new_user() to always return 0 causes the RHEL5 client to make it one step further such that it then fails at registerServer2. Stubbing out same doesn't change RHEL3 or 4 client behavior. [Tue Dec 12 17:24:32 2006] rhn_register Traceback (most recent call last): File "/usr/share/rhn/up2date_client/tui.py", line 1229, in __init__ other = self.tui.other) File "/usr/share/rhn/up2date_client/rhnreg.py", line 367, in registerSystem2 other) File "/usr/share/rhn/up2date_client/rhnserver.py", line 62, in __call__ message = pieces[2].strip(" '") exceptions.IndexError: list index out of range
I reproduced the issue and figured out a work-around. For some reason the PyPAM module needs to have pam-devel installed in order to work. We're still trying to figure out why exactly that is, but as a work-around you can do an 'up2date pam-devel' on the satellite followed by a satellite restart and rhn_register should work for PAM authenticated users.
John, yes, thanks, this workaround does work for me too. Thanks for your quick response! Leaving open until the root cause is found.
I saw something similar here. Sat. Server 4.1.5 wouldn't let me rhnpush my packages into a custom channel. I disabled PAM, and it worked. I added pam-devel and re-enabled PAM, and it also worked. So, maybe pam-devel should be a pre-requisite?
*** Bug 216865 has been marked as a duplicate of this bug. ***
Updated version of PyPAM released with satellite which includes a fix for PAM authentication working without requiring pam-devel. This will be releasd with RHN Satellite 5.0
QA Verified - can now register w/ PAM-auth'ed users.
release_pending
Closed for Satellite 500 Release.