Not recognizing incoming webhooks which use JWT

Questions
1

Describe the problem/error/question

I am trying to use a webhook trigger. The webhook is being sent with JWT HS256. When the n8n trigger is configured for JWT HS256 the webhook is not registering. When I change the n8n trigger to no authentication the webhook registers and delivers a JWT encoded attachment. If I load that attachment into the https://jwt.io debugger it decodes properly and the passphrase matches what I have put in the n8n JWT auth settings.

So we know that the external service is hitting the webhook with a properly signed JWT encoded message. We know that n8n is receiving the webhook. We don’t know why n8n is not registering the webhook when JWT auth is configured.

What is the error message (if any)?

n/a

Please share your workflow

Share the output returned by the last node

n/a

Information on your n8n setup

  • n8n version: 1.63.4
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): not set in .yml, assuming default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 22.04.5 LTS

Debug info

core

  • n8nVersion: 1.63.4
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.0
  • database: sqlite
  • executionMode: regular
  • concurrency: -1
  • license: community
  • consumerId: unknown

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

Generated at: 2024-10-23T18:29:16.452Z

2

hi @dmeledones

Just made a simple test with your node and it’s properly recognizing the signed JWT once I added the proper secret to the configs:

image
image2466×1550 201 KB

What steps have you taken so far to configure the node? Do you have the correct secret?

3

This is very interesting. I did configure JWT as shown in your screenshot and I do believe the secret is correct. I even changed it on both ends to a single word passphrase and confirmed with jwt.io that it updated on the sending side. Is it possible to view the secret in n8n? I tried pasting it and typing it but I have no way of knowing if it is somehow becoming corrupted.

As this is a new install I have destroyed the VM and will try again with a fresh setup soon, hopefully today.

4

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