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.
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 ^,?.
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.
AO 3/7/08-- need to check this again
If you forget Zip-- you get:
* ZIP / Postal Code is required.
* Message not found.
Thanks, Amy, for spotting the missing localization entry. This is now submitted in
Ok now-- all set on dev