Bug 96986

Summary: rhn_register does not allow non-alphanumeric characters in the password
Product: [Retired] Red Hat Linux Reporter: Eric West <ewest>
Component: rhn_registerAssignee: Adrian Likins <alikins>
Status: CLOSED CURRENTRELEASE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: gafton, jbills, mihai.ibanescu, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: current RHN Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-04 18:36:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric West 2003-06-07 20:57:55 UTC
Description of problem:

My password on RHN contains a non-alphanumeric character (e.g. "#"). I have no
problem logging on to RHN via a browser. However, the rhn_register application
refuses to accept the same set of password characters allowed on the RHN site.

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

 up2date v3.1.23 rel 1

How reproducible:

  repeatable

Steps to Reproduce:
1. create a password on rhn (ex. zazo#xxx)
2. confirm rhn login works with the password
3. exec rhn_register with the same username and password used in (2)
    
Actual results:

Problem registering user name:

Error Message:
    password contains character `#'
Error Class Code: 15
Error Class Info: The username contains invalid characters.
Explanation: 
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.redhat.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.

Expected results:

   rhn_register succeeds

Additional info:

Comment 1 Jim Bills 2003-08-30 23:33:21 UTC
This bit me too using up2date v3.1.23 rel 2. Work-around: changed password to less
secure password on rhn. Sigh...

Comment 2 Adrian Likins 2005-10-04 18:36:12 UTC
fixed via server side changes