HTTP Request Authorization Issue after N8N Update

Hello. My internal HTTPS requests are now failing after the N8N update. Please help.
http://localhost:5678/rest/executions-current

{
"status": "rejected",
"reason": {
"name": "StatusCodeError",
"statusCode": 401,
"message": "401 - "Unauthorized"",
"error": "Unauthorized",
"options": {
"timeout": 3600000,
"headers": {...}, // 1 keys
"method": "GET",
"uri": "http://localhost:5678/rest/executions-current",
"gzip": true,
"rejectUnauthorized": true,
"json": true,
"auth": {...}, // 2 keys
"simple": true,
"resolveWithFullResponse": false,
"transform2xxOnly": false
},
"response": {
"statusCode": 401,
"body": "Unauthorized",
"headers": {
"x-powered-by": "Express",
"date": "Fri, 18 Mar 2022 18:41:04 GMT",
"connection": "close",
"transfer-encoding": "chunked"
},
"request": {
"uri": {...}, // 12 keys
"method": "GET",
"headers": {...} // 3 keys
}
}
}
}

Probably because you enabled user management, now the routes are protected by the authentication middleware. We are working on an official API.

3 Likes

@RicardoE105 Hi, is there a workaround for this? We are checking to see if The workflows are running and now all of them are broken. Please help!

Hi @Michael_Smith,

I haven’t tried this myself but I’ve seen this post recently on how to use the Rest API with user management: How to authenticate for REST API with Users management activated?