Google OAuth 2.0 - Problem creating credential

Questions
1

Describe the problem/error/question

I am trying to set up a Google Firebase Cloud Firestore account, i have sat up a client in Google cloud and have the client ID and the client secret.
The key is longer than the permitted length in n8n.
I have noticed that it seem google have updated the platform, the n8n docs differs from the Google cloud platform now.

What is the error message (if any)?

Problem creating credential

String must contain at most 32 character(s)

1 Like
2

We noticed this as well, GCP has updated their UI I believe too.

I did not notice the string length issue tho.

Could you confirm you are on the latest n8n or cloud?

It would be a weird temp solution, but if this length check is done via the browser, I could potentially provide a workaround tomorrow.

What credential value are you inputting that is longer than 32 characters?

3

i’m hitting the same issue.

4

@Make what key value is this being input into for the connection?

5

I have the same problem. For now it accepts 32 characters in type field, and secret has 35. Altering table gave no effect (probably some validation in code also).

6

I experience the same issue. Is there any workaround or solution in plan?

7

Dang. That’s good to know. Okay I wasn’t able to find a bug report on the n8n github, but one might need to be created.

8

Do you create it or should I?

9

You can try.

10

Created: Google Firebase Firestore/Realtime Database credentials 32 chars limit · Issue #13948 · n8n-io/n8n · GitHub

1 Like
11

I ran into the same thing. I found an entry indicating this was a problem back in 2021 as well. There was a suggested workaround then, don’t know if that’ll do you any good (it’s beyond me):

1 Like
12

Not work for me.

13

A fix for this has been merged and will be available in the next release.

The fix itself can be found here: fix: Allow saved credentials types of up to 128 characters instead of 32 by Joffcom · Pull Request #13985 · n8n-io/n8n · GitHub

14

Has there been any update to this issue or a temporary workaround in the meantime? I see the last message was from 4 days ago.

15

Hey @alabrida

As mentioned above… the fix has merged and will be available in the next release. We release new versions on a Monday unless an issue is urgent, the fix for this will be part of tomorrows release.

16

Same problem even with 1.84.1 ver

17

same problem with 1.84.3, but getting this when trying to setup LinkedIn Authentication with Community Management

18

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