Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Bug 1330838

Summary: [RFE] Should give more friendly info when password is not acceptable
Product: Red Hat Enterprise Linux 7 Reporter: wanghui <huiwa>
Component: cockpitAssignee: Dominik Perpeet <dperpeet>
Status: CLOSED ERRATA QA Contact: Jan Ščotka <jscotka>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: bugs, cshao, fdeutsch, huzhao, leiwang, stefw, weiwang, yaniwang
Target Milestone: pre-dev-freezeKeywords: Extras, FutureFeature
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-0.114-2 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-04 13:47:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1329957    

Description wanghui 2016-04-27 06:29:39 UTC
Description of problem:
Should give more friendly info when password is not acceptable. It should be the prompt that which format of password can be accepted.

Version-Release number of selected component (if applicable):
ovirt-node-ng-installer-ovirt-3.6-2016042500.iso 
cockpit-0.103-1.el7.centos.x86_64
cockpit-ovirt-0.5.1-0.0.master.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Anaconda install NGN 4.0.
2. Start cockpit service.
3. In Accounts page, create a new account and set the password like "redhat".

Actual results:
1. After step3, it can not create the new account and give the error like follows.
"Password is not acceptable"

Expected results:
1. It should give more friendly info when the password is not acceptable. It should be better to prompt that which format of password can be accepted.

Additional info:

Comment 1 Stef Walter 2016-04-27 08:45:40 UTC
By calling pwscore with a { err: "message" } we can retrieve the message from that process and display it instead of a stock message.

Comment 3 Stef Walter 2016-07-08 15:10:09 UTC
Upstream work: 

https://github.com/cockpit-project/cockpit/pull/4699

Comment 4 Stef Walter 2016-07-09 07:08:17 UTC
Merged upstream. This will be part of Cockpit 0.114

Comment 6 Stef Walter 2016-07-14 12:21:43 UTC
Cockpit integration test here: https://github.com/cockpit-project/cockpit/blob/master/test/verify/check-accounts#L110

Comment 9 errata-xmlrpc 2016-08-04 13:47:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-1442.html