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

Bug 514759

Summary: RHN Activation Key -- white space nuisance
Product: Red Hat Satellite 5 Reporter: Clifford Perry <cperry>
Component: ServerAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Garik Khachikyan <gkhachik>
Severity: medium Docs Contact:
Priority: medium    
Version: 501CC: cperry, gkhachik, mkoci, rmunilla, tao, xdmoon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 448638 Environment:
Last Closed: 2010-02-16 08:40:01 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:
Bug Depends On:    
Bug Blocks: 518256    

Comment 1 Clifford Perry 2009-07-30 16:35:59 UTC
This bug was cloned to track that if you use white space within the activation key - the resulting key will not function. We should either fix code to remove all white space - or modify backend/client code to pass along the white space correctly and allow it. I am happy with either solution. 

Cliff

Comment 5 Justin Sherrill 2010-01-13 18:53:45 UTC
fixed in master for spacewalk:  1d9847af191e625f6831a344947eb1371ac75997

basically just strip out all whitespace when creating/updating a activation key.  You will need to update any existing keys.

Comment 8 Garik Khachikyan 2010-02-05 13:17:25 UTC
# VERIFIED

Applied a check against Satellites installed on RHEL4 and RHEL5 servers. The
packages of brew build fixed the issue:
spacewalk-java-0.5.44-65.el[4,5]sat
spacewalk-backend-0.5.28-39.el[4,5]sat

Currently there is not possible to have trailing <space>-s while creating/modifying the activation keys... All they are striping.

Comment 10 errata-xmlrpc 2010-02-16 08:40:01 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0105.html