Bug 1032321

Summary:	RFE: Client error message Incorrect username/password should be replaced with Incorrect username/apikey
Product:	[Retired] Zanata	Reporter:	Ding-Yi Chen <dchen>
Component:	Component-Maven	Assignee:	Michelle Kim <mkim>
Status:	CLOSED UPSTREAM	QA Contact:	Zanata-QA Mailling List <zanata-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.1	CC:	zanata-bugs
Target Milestone:	---	Keywords:	screened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-29 02:11:49 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:

Description Ding-Yi Chen 2013-11-20 00:55:45 UTC

Description of problem:
Clients do not use password in most cases, instead, they use apikey.
And error message should ask for correct apikey instead
of password

Version-Release number of selected component (if applicable):
org.zanata:zanata-maven-plugin:3.1.2:

How reproducible:
Always

Steps to Reproduce:
1. mvn -e zanata:push -Dzanata.user=NotExists

Actual results:
[ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:3.1.2:push (default-cli) on project standalone-pom: Zanata mojo exception: Incorrect username/password -> [Help 1]


Expected results:
[ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:3.1.2:push (default-cli) on project standalone-pom: Zanata mojo exception: Incorrect username/apikey -> [Help 1]


Additional info:

Comment 1 Ding-Yi Chen 2015-03-23 02:57:33 UTC

Even if -Dzanata.disableSSLCert is specified, it returned like.


[WARNING] SSL certificate verification will be disabled. You should consider adding the certificate instead of disabling it.
[WARNING] exception processing request
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated

[ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:3.4.2:push (default-cli) on project standalone-pom: Zanata mojo exception: IOException: peer not authenticated -> [Help 1]

It would be more straight forward and less confusing if the error message is
Incorrect username/apikey

Comment 2 Zanata Migrator 2015-07-29 02:11:49 UTC

Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-150