Custom Auth not saving

Questions
1

Describe the problem/error/question

Hello,

i have the Problem that since Update 2.13.3 the Custom Auth Credentials not saving anymore.

I can click edit enter anything in the JSON Field, click on Save and after a reload the JSON Field is empty again.

I updated to 2.13.4, but the problem persists.

For example the JSON from the Doc:

image
image711×498 20.7 KB

After Saving and reopening.

image
image557×334 11.3 KB

image
image558×253 6.17 KB

Information on your n8n setup

  • n8n version: 2.13.4
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Debian 13
2

Hi @LycaKnight

If the goal is just to send static headers, I’d recommend using Header Auth instead, since this method is officially supported in HTTP Request credentials.

3

I need to add the following to the Credentials (and update the credentials regularly via n8n api key)
which worked perfectly before 2.13.3
I can’t imagine it’s intended for all the entries to disappear after saving.

I tested it on 2 different n8n instances as soon as i update to 2.13.3 it is not possible to use Custom Auth. After saving and reload the page the entries are empty again.

{
  "data": {
    "json": "{\"headers\":{\"Authorization\":\"Bearer XXXX\"},\"qs\":{\"client_id\":\"XXXX\",\"client_secret\":\"XXXX\",\"refresh_token\":\"XXXX\",\"scope\":\"XXXX\"}}"
  }
}
4

I found one somewhat related GitHub issue, #12596, about auth credentials being reset after save, but it was for Header Auth on an older version and does not look like an exact match for your Custom Auth case on 2.13.3/2.13.4.

So from what I can see, I don’t think there is already a clearly matching GitHub issue for this exact behavior. This may be worth opening as a new bug report with your version, repro steps, and the minimal JSON example.

5

I am experiencing the same behavior, self hosted on version 2.15.0 → I am therefore unable to rotate my secrets. Are there any updates on this issue?

6

I have it on 3 different servers now.
But I tested it, it is fixed on 2.16.0 (beta at the moment).

So you can upgrade to beta or wait for the normal release :slight_smile:

1 Like