fix(GraphQL Node): Refresh OAuth2 token when it expires #17891
Merged
+138
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fix an issue where the OAuth2 access token is not refreshed in the GraphQL node when receiving a 401
Dummy NodeJS server that can be used to test the refresh logic:
Add an OAuth2 credential with
Authorization URL: http://localhost:3000/authorize
andToken URL: http://localhost:3000/token
(client ID and secret can be whatever) to test with this code. Before the fix the GraphQL would not try to refresh the token after getting a 401, after the fix - it doesRelated Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-1766/graphql-node-not-refreshing-oauth2-token-in-graphql-node
https://community.n8n.io/t/n8n-not-refreshing-oauth-token-in-graphql-node/54363/2
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)