Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1046708

Summary: rhnreg_ks - old password is accepted and system is registered in Spacewalk
Product: [Community] Spacewalk Reporter: Curtis <curtis>
Component: ClientsAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-03 15:20:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1484117    

Description Curtis 2013-12-26 17:10:28 UTC
Description of problem:
rhnreg_ks registration works with an old password. If password is reset and old password is used with registration command it succeeds. 

Version-Release number of selected component (if applicable):
1.9

How reproducible:
100% of retries.

Steps to Reproduce:
1. Use rhnreg_ks to register a server with the Spacewalk server using --password
2.rhnreg_ks --username=admin --password=<prvious_password> --serverUrl=http://spacewalk/XMLRPC --activationkey="hi_hello" --force
3.

Actual results:
Server is registered to Spacewalk with old password.

Expected results:
Rejection of registration process due to invalid password.

Additional info:

Comment 1 Milan Zázrivec 2014-01-03 15:20:38 UTC
As long as you use activation key to register your clients, any
user / password information passed in to rhnreg_ks is no longer relevant
and your system will be registered based on the activation key used.

Without the activation key, the old password will not be accepted, just
as you would expect.

Closing with not a bug.

Comment 2 Eric Herget 2017-09-28 18:09:06 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.