Bug 1329937

Summary:	UX: Obscure 'API authentication failed' message when trying to log in with incorrect password
Product:	Red Hat CloudForms Management Engine	Reporter:	Jan Krocil <jkrocil>
Component:	API	Assignee:	Yuri Rudman <yrudman>
Status:	CLOSED ERRATA	QA Contact:	Jan Krocil <jkrocil>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.6.0	CC:	hkataria, jhardy, mpovolny, obarenbo, simaishi, sshveta
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ui
Fixed In Version:	5.6.0.5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-29 15:53:41 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:

Description Jan Krocil 2016-04-25 06:14:20 UTC

Description of problem:
SSIA

Version-Release number of selected component (if applicable):
5.6-beta2.3

How reproducible:
Always

Steps to Reproduce:
1. Use incorrect creds and try to log in, multiple times

Actual results:
'API authentication failed' message(s), stacking with every unsuccessful attempt.

Expected results:
A single 'Incorrect username or password' (or similar, more descriptive) message.

Additional info:
'API authentication failed' is not helpful at all. Does that mean the API could not be reached? Does it mean an internal error happened when processing the login request? Does it mean the login or password were simply incorrect?

Comment 2 Jan Krocil 2016-04-25 07:00:10 UTC

There already is a bugzilla for the multiple messages here https://bugzilla.redhat.com/show_bug.cgi?id=1327042.

This BZ is to address the obscurity of the error message.

Comment 3 Dave Johnson 2016-04-27 03:32:39 UTC

*** Bug 1330326 has been marked as a duplicate of this bug. ***

Comment 4 Yuri Rudman 2016-05-03 13:09:49 UTC

PR merged: https://github.com/ManageIQ/manageiq/pull/8274

Comment 5 Jan Krocil 2016-05-05 07:36:32 UTC

Verified fixed in 5.6.0.5-beta2.4.20160503153816_1fb554f.

Comment 7 errata-xmlrpc 2016-06-29 15:53:41 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://access.redhat.com/errata/RHBA-2016:1348