Quick answer
401 means : The HTTP 401 Unauthorized client error status response code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.
So, possible causes are:
- incorrect credentials
- jenkins incorrect credentials injection or jenkins bug
- mule-maven-plugin:2.2.1 bug
Validate credentials
Jenkins or mule-maven-plugin bug are not common. Human error is very common.
In order to validate who is causing the error?, I advice you validate your credentials directly to Anypoint http url
Anypoint login url
Reviewing the plugin official source code v2.2.1 related to your stacktrace ArmDeployer.deploy(ArmDeployer.java:38) :
https://github.com/mulesoft/mule-maven-plugin/tree/v2.2.1
And its classes (in this order):
I got the base url:
ArmApi(null, "https://anypoint.mulesoft.com", USERNAME, PASSWORD, ENVIRONMENT, "", false);
And with this url, I found this authentication request snippet:
curl -H "Content-Type: application/json" -X POST -d '{"username":"jane","password":"doe"}' https://anypoint.mulesoft.com/accounts/login
Also in this web , another ways to authentication are showed:
- form params
- bearer(used for mule-maven-plugin:2.2.1)
Direct authentication: success
If https://anypoint.mulesoft.com/accounts/login returns you a successful answer, will indicate that there are some error at credentials manager in your jenkins or just an error in the human jenkins admin.
Direct authentication: failure
If https://anypoint.mulesoft.com/accounts/login returns you an error answer like your 401 Unauthorized, will indicate that mule-maven-plugin:2.2.1 and jenkins are good, and your credentials are wrong!!! or maybe they expired.
Anyway just to try, reset the credentials or ask for a new user/password.
thank you very much for sharing this. I did tried with creds and its giving unauthorized error via curl. But we are using Okta for sign-in to mulesoft. so i guess we should use bearer method (first get saml response and then get token). I got the saml response but not sure how to proceed after that
I saw the Bearer token in some classes of mule-maven-plugin v2.2.1, so I think you can review if it is possible to use bearer instead user/password. Also you could try with a more recent version of this plugin. In another way, I think okta is for interactive login for human users. But for non-interactive users (background process like jenkins) I think mule-maven-plugin requires user/password or some kind of long lived api-key
created a new account in anypoint platform without MFA( no single sig on ) and used the creds in settings.xml , It started working.
Glad I helped find the problem.