Bug 841499

Summary:	[RFE] SAM UI while creating a new user accepts password same as username created
Product:	[Retired] Subscription Asset Manager	Reporter:	Tazim Kolhar <tkolhar>
Component:	katello	Assignee:	Bryan Kearney <bkearney>
Status:	CLOSED WONTFIX	QA Contact:	Tazim Kolhar <tkolhar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.2	CC:	cwelton, esammons, gstoecke, tomckay
Target Milestone:	rc	Keywords:	FutureFeature, TestBlocker, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	849226 (view as bug list)		Environment:
Last Closed:	2012-10-29 17:41:54 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:
Bug Blocks:	816564, 849226

Description Tazim Kolhar 2012-07-19 08:03:26 UTC

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 1 Tom McKay 2012-10-29 17:41:54 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