Authorization headers are not passed through correctly on n8n (both Bearer and Custom)

Questions
1

NOTE: This is a known bug that is being disregarded even on your GitHub, so it would be great if you finally looked into it.

I’m trying to create an HTTP node that would send an http request to an internal API.

When I add an authorization token via Bearer authentication or via Custom authentication (using “Authentication”: “Bearer token_value”), your software resets the token and doesn’t send anything. So the authorization field is sent empty!

It does not provide any error about it, nothing, so I end up wasting time trying to understand what happened and could only uncover the error because I was sending the request to my own server to check what happens.

The only way to fix that is to ask n8n to not send any authorization values at all and to instead send the request via Headers using the “Authorization”: “Bearer token_value” (which would not work for most cases and is less secure).

Could you please fix this error finally?

This is ridiculous it’s still there especially that many users reported it multiple times on this forum and nothing happened. Here are some links below:

  1. HTTP Request Node Not Sending Authorization Header Despite Selecting Connected OAuth2 Credential (TikTok API)

  2. HTTP Request Module Not Passing Authentication

Information on your n8n setup

  • n8n version:
  • 1.89.2 (your cloud)
  • Database (default: SQLite):
  • using your cloud version
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • own
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • your cloud app
  • Operating system:
  • Mac OS X, Chrome browser
2 Likes
2

Hi @InfraNodus

I think it’s fixed in versions > 1.92.0

3

Thanks for the response!

So that means I should just better use the open source version than the cloud hosted version?

4

Hi @InfraNodus

The latest stable version of the n8n cloud is 1.93.0

image
image951×678 42.4 KB

So, you just need to update your n8n cloud.

5

Hi! I did the update, but it’s not working for me. When I provide the Http Bearer auth key I get the error:

The type httpBearerAuth is not supported

1 Like
6

Hi @InfraNodus

Could you please share your use case along with a sample workflow? I will try to replicate the issue on my end…

7

Thank you! The Bearer authorization is not working in the HTTP nodes even though when I make the same requests using Make.Com or Postman or any other way they work just fine. That’s why in this template I had to send the Authorization headers manually. Would like to avoid that.

and also here’s a demo video of how it works on my end:

8

Hi @InfraNodus

Your currently attached workflow is using three outdated nodes:

  • AI Agent Node
    image

  • Model Node
    image

  • HTTP Tool Node, which is causing the error because it’s deprecated
    image

Everything should work smoothly once you switch to the latest versions of these nodes.

I’ve gone ahead and updated the workflow for you:

⚡

:point_right: If this solves your problem, kindly mark my reply as the solution :white_check_mark::pray:t2:

1 Like
9

Thanks! Changing the versions worked! I think i reused them from other workflows so perhaps there should be some visible notification in n8n when you’re using deprecated nodes to avoid these problems.

11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.