Publishing API returns 401 'Authentication Failed' with valid user token

Yesterday, I started getting 401 ‘Authentication Failed’. However, I didn’t change anything on my build script, and I’ve been able to publish to Central Repository for 20+ days straight.

I even generated a new user token and tested it by calling the status API, and the result was the same:

curl --request POST --verbose --header 'Authorization: UserToken {UserTokenValue}' '{deploymentId}'

// Response: 401
  "error": {
    "message": "Authentication Failed"

Has anybody experienced the same issue? I also tested using Bearer instead of UserToken on the Authorization header.

1 Like

It’s working again. It was probably a service disruption.