Coursera 401 error

Not applicable

I get an error 401 Unauthorized, in Coursera, Lab 1

Topic: Deploy the edge-developer-training-backend proxy and dependencies.

Step: node setup

Has anyone experiened this before, what could be the problem?

7548-coursera1.png

7549-coursera2.png

7551-coursera3.jpg


Error message in text:


Request prepared for the server ************************** GET https://api.enterprise.apigee.com/v1/organizations/############/apis/edge-developer-training-idp/dep... accept: application/json accept-encoding: gzip authorization: Basic [Not shown in log] [INFO] Request prepared for the server ************************** GET https://api.enterprise.apigee.com/v1/organizations/############/environments/test/targetservers accept: application/json accept-encoding: gzip authorization: Basic [Not shown in log] [ERROR] 401 Unauthorized [INFO] =============Importing App================ [INFO] Request prepared for the server ************************** POST https://api.enterprise.apigee.com/v1/organizations/############/apis?action=import&name=edge-develop... accept: application/json accept-encoding: gzip authorization: Basic [Not shown in log] content-type: application/octet-stream [Request body contains data, not shown] [ERROR] 401 Unauthorized [ERROR] * * * * * * * * * * * This deployment could have failed for a variety of reasons. * * * * * * * * * * * [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 17.917 s [INFO] Finished at: 2018-10-10T13:05:50+02:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal io.apigee.build-tools.enterprise4g:apigee-edge-maven-plugin:1.1.6:deploy (deploy-bundle) on project edge-developer-training-idp: : MojoExecutionException: 401 Unauthorized -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException (node:8632) UnhandledPromiseRejectionWarning: #<Object> (node:8632) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:8632) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [ERROR] 401 Unauthorized [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 18.385 s [INFO] Finished at: 2018-10-10T13:05:51+02:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.apigee.edge.config:apigee-config-maven-plugin:1.2.1:targetservers (create-config-targetserver) on project edge-developer-training-backend: Apigee network call error 401 Unauthorized -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException (node:8632) UnhandledPromiseRejectionWarning: #<Object> (node:8632) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

0 3 698
3 REPLIES 3

Hi @Morten Nielsen - Since its a 401, I believe its something to do with the credentials. Can you confirm if you typed them correctly ?

I have both tried to type and copy/pasted the apigee username and password - same result, 401.

I just changed my password - now it works 😐
My old password not working, it had these chars (random order): gLB%v^DpRf0A5q3Eb14R