Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Just a nitpick. If user enters the same string for pass/confirm pass as they enter for username, it should be dinged right away, even if it is a good, "long" password

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


How reproducible:


Steps to Reproduce:
1.  Begin creating a new user.  enter the username "bobthebuilder"
2.  Enter "bobthebuilder" for pass/confirm pass as well.
3.  View password strength bar.
  
Actual results:
Strong password! 

Expected results:
Even if we allow it, we shouldn't be saying it's a strong password.

Additional info:

4b0c858b77aeb4f0ec888f14bdab3747abace23f

made it throw a warning and turn red if the password contains the username at all.

QA Verified.

getting rid of 6.0.0 version since that doesn't exist