Bug 975484 - Some characters no longer allowed in Org names
Summary: Some characters no longer allowed in Org names
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Adam Price
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-18 14:51 UTC by Jeff Weiss
Modified: 2014-11-09 22:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-18 20:52:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jeff Weiss 2013-06-18 14:51:41 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
1.4.2-1.git.682.7662991.el6

How reproducible:


Steps to Reproduce:
1.  Create an org
2.  As org name enter the following character: ↽
3.

Actual results:
Name cannot contain characters other than alpha numerals, space, '_', '-'

Expected results:
Org created

Additional info:
Other characters do work, eg 䘦 or ᅈ
Seems like the range of allowed characters has been restricted, I am not familiar enough with UTF8 to know whether legitimate names in non-latin languages will be disallowed because of this, but it appears to be the case.
Comment 1 RHEL Program Management 2013-06-18 15:04:52 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Jeff Weiss 2013-06-18 17:53:14 UTC 
Note another thing that was broken with the same change in katello, was orgs with a "." in the name.

So another testcase is to create an org called "foo.bar".  It should succeed.
Comment 4 Adam Price 2013-06-18 19:39:56 UTC 
everything should be allowed except <, >, and /
Comment 5 Jeff Weiss 2013-06-18 20:52:18 UTC 
Superseded by 975593
Note You need to log in before you can comment on or make changes to this bug.