Digest Auth returns 401 in n8n (but works fine with Postman and cURL)

Questions
1

I’m trying to connect to a Shopware 5.2 API endpoint that only supports Digest Auth.
With Postman, setting Digest Auth works perfectly and returns HTTP 200.
Using cURL on my local machine also returnes 200.

However, in n8n, I always get 401 - “Invalid or missing auth”, even though I am using the exact same credentials in an HTTP Request node set to Digest Auth. I have tested it both on the cloud version of n8n and on a self-hosted instance with Docker Compose. The result is always 401, while Postman and cURL both succeed with 200.

Here is what I have tried so far:

  1. Double-checked credentials (Shopware backend user with API access, correct username and API key, etc.)
  2. Made sure the URL matches exactly (including www vs non-www).
  3. Removed all extra headers, only sending Accept: application/json.
  4. Tried setting a custom User-Agent like PostmanRuntime/7.x.
  5. Set the environment variable N8N_USE_DEPRECATED_REQUEST_LIB=true in Docker Compose, then restarted the container.
  6. Tried Basic Auth just to check, which also fails.

I am stuck with n8n returning 401 while cURL and Postman get 200. The Shopware server definitely expects standard Digest Auth. Has anyone else encountered a similar issue with Digest Auth in n8n, especially with Shopware 5.2? Are there any additional workarounds or advanced settings that could make n8n’s HTTP Request node behave the same way as cURL or Postman?

Eventually, this must run on the self-hosted version, but I have already verified the same issue exists on n8n cloud. Any suggestions or insights would be greatly appreciated.

Thanks in advance!

2

Hi, could you paste your workflow? But be careful not to expose you credentials.
If you need some hints on setting up credentials you could check this post

It seems like somehow it’s not using the credentials.

3

I have literally no clue why it would fail. As I said, I tried out everything that came in my mind and with cURL and Postman the Request works perfectly fine…

4

There seems to be a space at the end of the URL

CleanShot_2025-03-13_at_09.04.50
CleanShot_2025-03-13_at_09.04.50790×660 37.1 KB

Usually that’s not a problem but worth checking if that is your problem.
Also try adding a / after articles. I have had some API’s not liking the request without trailing /.

5

Sadly removing the space or adding a slash doesn’t make any difference