Bug 849226

Summary:	[RFE] SAM UI while creating a new user accepts password same as username created
Product:	Red Hat Satellite	Reporter:	Eric Sammons <esammons>
Component:	Content Management	Assignee:	Tom McKay <tomckay>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	esammons, mmccune, tkolhar
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	841499	Environment:
Last Closed:	2012-10-03 15:29:03 UTC	Type:	Bug
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:	841499
Bug Blocks:

Description Eric Sammons 2012-08-17 18:13:32 UTC

+++ This bug was initially created as a clone of Bug #841499 +++

Description of problem:
While creating a new user . if password entered is same as username it is 
accepted, while usually passwords should be different from username 

Version-Release number of selected component (if applicable):
[root@nec-em9 ~]# rpm -qa | grep katello
katello-certs-tools-1.1.6-1.fc16.noarch
katello-configure-0.2.30-1.fc16.noarch
katello-headpin-all-0.2.24-1.fc16.noarch
katello-selinux-0.2.6-1.fc16.noarch
katello-cli-common-0.2.43-1.fc16.noarch
katello-glue-candlepin-0.2.45-1.fc16.noarch
katello-cli-headpin-0.1.19-1.fc16.noarch
katello-headpin-0.2.24-1.fc16.noarch
katello-common-0.2.45-1.fc16.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch

How reproducible:
yum install -y katello-headpin-all
katello-configure --deployment=sam

Steps to Reproduce:
1.Login to SAM webUI
2.Navigate to Administer
3.Users tab
4.Click on Create new user
5.Enter username
6.enter password which is same as username created
7.Confirm password
8.enter mail id
9,enter the organisation and environment
10.create the user
11. User is created
  
Actual results:
The user is created successfully and the password field accepts
username as password

Expected results:
The password same as username should not be acceptes as
usually password are different from the username
A password validation should be there

Additional info:

Comment 2 Mike McCune 2012-10-03 15:29:03 UTC

Based on feedback in our triage session we decided that this isn't a feature we will likely implement in the near term.  If customers demand customizable password policy we can re-open.