Bug 1372012 - Login fields disabled upon failed login attempts.
Summary: Login fields disabled upon failed login attempts.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: GA
: cfme-future
Assignee: Harpreet Kataria
QA Contact: Mike Shriver
URL:
Whiteboard: auth:miqldap:webui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-31 17:22 UTC by amogh
Modified: 2018-09-20 11:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-20 11:55:10 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
ldaptest (60.90 KB, image/png)
2016-08-31 17:22 UTC, amogh
no flags Details

Description amogh 2016-08-31 17:22:52 UTC
Created attachment 1196476 [details]
ldaptest

Description of problem:
Login fields disabled upon failed login attempts. Login page does not auto refresh upon failed login attempt. This is observed with ldap configuration. 

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

How reproducible:
always.

Steps to Reproduce:
1. Login as admin and configure cfme auth for "ldap"
2. try to login as ldap user display name, enter wrong password. Try the failed attempt twice.
3. Observe that the login "username" and "password" fields are disabled. 
4. Manual refresh is needed to enter the new values for username and password.
This affects cfmeqe test automation scripts.

Actual results:
Login fields disable upon failed login attempt. Refer the ldaptest.png screenshot.


Expected results:
Fields need not be disabled. It blocks if admin user wants to login and change configurations. 

Additional info:

Comment 3 Josh Carter 2018-09-20 11:55:10 UTC
Bug Closure

Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!


Note You need to log in before you can comment on or make changes to this bug.