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 1042988

Summary: Log In Failure String Could Use Some Attention
Product: Red Hat Enterprise Linux 7 Reporter: Matt Reid <mreid>
Component: redhat-access-guiAssignee: Dan Varga <dvarga>
Status: CLOSED CURRENTRELEASE QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: kroberts, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: redhat-access-gui-1.0.0-5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 10:29:31 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:
Attachments:
Description Flags
Failure String none

Description Matt Reid 2013-12-13 17:05:03 UTC
Description of problem:
The Failure string isn't very consistent either. After failing, it says "login failed. Please try again". If there's a period in it, it seems like the L in login should be capitalized, especially since the "Show Password" checkbox starts with a capital, and the "Please try again" text starts with a capital. It also seems a little odd that the first part of the message ends in a period,
but the second piece ends without any punctuation.

Some of this will depend on if anything happens with the terminology used on this screen (see BZ 1042931), but either the current string could use some clean up, and instead read "Log in failed, please try again." or it should match the message used on Portal itself and save us some translation and string management and say "Username or password was invalid".

Version-Release number of selected component (if applicable):
redhat-access-gui-1.0.0-3.el7

How reproducible:
100%

Steps to Reproduce:
1. Enter invalid credentials and try to log into RH Access Gui

Actual results:
Awkward string is shown

Expected results:
String to match what we return on failed log in on Portal, or a properly capitalized string

Additional info:

Comment 2 Matt Reid 2013-12-13 17:06:13 UTC
Created attachment 836409 [details]
Failure String

Comment 3 Dan Varga 2014-02-07 14:22:11 UTC
This is now fixed in redhat-access-gui-1.0.0-5.  Need acks for new build.

Comment 4 Vladimir Benes 2014-02-25 15:12:52 UTC
Username or password was incorrect

Comment 5 Ludek Smid 2014-06-13 10:29:31 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.