Bug 251003 - bad phone numbers being sent to user service
Summary: bad phone numbers being sent to user service
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
(Show other bugs)
Version: RHN Stable
Hardware: All Linux
Target Milestone: ---
Assignee: Sebastian Skracic
QA Contact: Amy Owens
Whiteboard: US=16341
Depends On:
Blocks: 433460
TreeView+ depends on / blocked
Reported: 2007-08-06 14:02 UTC by Chris Duryee
Modified: 2008-04-07 20:00 UTC (History)
4 users (show)

Fixed In Version: 5.0.5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-07 20:00:39 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Chris Duryee 2007-08-06 14:02:58 UTC
Description of problem:

Something in RHN hosted is sending incorrect phone number data to user service.
Please adhere to the following rules regarding phone numbers:

- A phone with no numbers should be turned into null
- A "buy dell" phone number (contains BUYDELL) should be blanked out
- The following characters should be removed (^,?) (carat, comma, question mark)

Maybe you can validate the phone number against user service before sending it
in, we can discuss the best way to do this.

Comment 1 Jie Chen 2008-01-21 16:34:46 UTC
This was reproduciable.  I was able to create a new user with phone number that
has only one digit, and a new user with phone number that contains ^,?.

Comment 2 Sebastian Skracic 2008-03-06 19:41:10 UTC
A consent has been reached that all data transformations (such as converting BUYDELL 
into real number etc) should be performed within user service itself, and as such do 
not belong to RHN Hosted code.

To facilitate this approach, the core submitted in r118583 validates all contact info 
for RHN user creation against user service, including the phone numbers.

Comment 5 Amy Owens 2008-03-07 20:57:37 UTC
AO 3/7/08-- need to check this again

If you forget Zip-- you get:
    * ZIP / Postal Code is required.
    * Message not found.

Comment 6 Sebastian Skracic 2008-03-10 12:31:20 UTC
Thanks, Amy, for spotting the missing localization entry.  This is now submitted in 

Comment 7 Amy Owens 2008-03-10 15:16:48 UTC
Ok now-- all set on dev

Note You need to log in before you can comment on or make changes to this bug.