As Airtable is phasing out their API keys, I've been attempting to configure new Airtable OAuth2 credentials. Upon trying to establish a connection, the credential callback returned the following error:
{
"error": "invalid_request",
"error_description": "The "code_verifier" must only contain characters that are in: [A-Z] / [a-z] / [0-9] / "-" / "." / "_""
}
I noticed that PKCE support was introduced earlier this summer (feat(core): Add PKCE for OAuth2 by agobrech · Pull Request #6324 · n8n-io/n8n · GitHub), and I suspect this error indicates a necessary adjustment for the Airtable Auth2 credentials to be successfully created.
- callin.io version: 1.4.1
Hi, I'm very sorry you’re experiencing difficulties.
I was able to reproduce this, but this error only occurred sporadically, with about 2 out of 3 attempts succeeding. Therefore, I suspect this is simply a situation where Airtable is rejecting a character (typically supported by other services implementing OAuth2) in the codeverifier field. Retrying the connection should generate a new codeverifier.
Could you please try this again on your end and let me know if the problem also resolves for you upon retrying?
Interesting. I attempted a few more times, and it succeeded on the fourth try.
I suspect the core reason for this problem lies with pkce-challenge@3.0.0.patch, which eliminated the ~
character to resolve a Twitter-specific issue. You can find related discussion in PR #6324.
Hello,
We've also encountered this issue and plan to address it shortly.
I'm encountering the same problem.
I attempted to run a workflow and discovered that the Airtable authentication was failing. I generated new OAuth credentials, and while I can connect on the credentials screen, the nodes are prompting me to verify my credentials.
This thread was automatically closed 90 days following the last response. New replies are no longer permitted.