Bug 734610

Summary:	ldap users registering for RHQ with usernames of less than 6 characters fails
Product:	[Other] RHQ Project	Reporter:	Caerie Houchins <cdhouch>
Component:	Core UI	Assignee:	Ian Springer <ian.springer>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.0.1	CC:	ccrouch, hrupp, ian.springer, skondkar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:	678340, 730796

Description Caerie Houchins 2011-08-30 21:56:27 UTC

Description of problem:
When an existing ldap user tries to register with RHQ for the first time, and their username is less than 6 characters long, a red ! appears to the left of their username with the mouse over text reading "Must be at least 6 characters".  The admin user can create local users that have usernames of less than 6 characters, its just not an ldap login.

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

How reproducible:
Every time

Steps to Reproduce:
1. Create an ldap user whose username is less than 5 char
2. Login with this user to RHQ and attempt to register for the first time
  
Actual results:
cannot register

Expected results:
able to register

Additional info:

Comment 1 Ian Springer 2011-08-31 21:40:22 UTC

[master 5938708] fixes this. There is no longer any length restrictions on the username on the registration form.

It should be noted that the username field in the DB does have a maximum length constraint of 100 characters. I did not add a validator for that constraint, since it seems very unlikely to encounter LDAP usernames longer than 100 chars. However, one can easily be added if other people think it should be done.

Comment 2 Sunil Kondkar 2011-09-16 11:35:56 UTC

Verified on build#421 (Version: 4.1.0-SNAPSHOT Build Number: ad51846)

Registered and logged in to RHQ successfully as ldap user having user name less than 5 characters.

Marking as verified.

Comment 3 Mike Foley 2012-02-07 19:31:31 UTC

changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE

Comment 4 Mike Foley 2012-02-07 19:31:32 UTC

marking VERIFIED BZs to CLOSED/CURRENTRELEASE