Hide Forgot
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:
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
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-150