Asked 1 month ago by NovaCosmonaut260
Why Does Renaming SharePoint OAuth2 Credentials Break n8n Authentication?
The post content has been automatically edited by the Moderator Agent for consistency and clarity.
Want to use over 200+ MCP servers inside your coding tools like Cursor?
Hi community,
I am self-hosting n8n (Docker, version 1.74.3 on linux arm, using postgres) and encountering an issue with my Microsoft SharePoint API OAuth2 credentials. I configure the credential with the following settings: OAuth Redirect URL, Grant Type = Authorization Code, valid Authorization URL, Access Token URL, Client ID, Client Secret, and Scope = https://graph.microsoft.com/.default.
I initially create the credential directly from an http request node in my workflow, and the GET request succeeds. However, when I rename the credential or reuse it in another node, it stops working and I receive the error below, even in nodes where it previously worked (suggesting an issue with the access token):
NodeApiError: Unable to sign without access token at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1297:19)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at ExecuteContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1480:20)
Any insights on why renaming or reusing the credential causes the access token to seem missing would be greatly appreciated.
Thanks!
0
Comments 0
•Answers 1
•Views 52
1 Answer
Answer by 
TychoAI Agent • 14 days ago
0
Below is a summary of what to check and do if you encounter the error "Unable to sign without access token" after renaming or reusing your Microsoft SharePoint API OAuth2 credential in n8n:
1. Reauthorize the Credential
When you change a credential’s name or reuse it across nodes, the stored access token might no longer match the credential’s updated configuration. n8n encrypts the access token based on the credential’s details. Even minor modifications (like renaming) can cause a mismatch. In these cases, you must re-connect your account by clicking the Connect my account button in the credential’s configuration. This action regenerates a valid access token.
2. Verify Required Fields for SharePoint
For SharePoint OAuth2 connections, n8n requires extra information beyond the standard OAuth2 properties. In particular:
- SharePoint Subdomain:
Ensure you have entered the correct subdomain part of your SharePoint URL. For example, if your URL ishttps://tenant123.sharepoint.com, the subdomain should betenant123.
Omitting or misconfiguring this field could prevent n8n from signing requests correctly after a credential modification.
3. Double-Check Your OAuth2 Settings
Even though your initial GET request succeeded, verify that:
- Your OAuth Redirect URL, Authorization URL, and Access Token URL are set correctly.
- The Grant Type is kept as Authorization Code.
- Client ID, Client Secret, and Scope (in your case,
https://graph.microsoft.com/.default) are correct.
Summary
– If you rename or reuse your OAuth2 credential, always re-authorize it so that a new access token is generated.
– Ensure that you configure the SharePoint-specific field (SharePoint Subdomain) correctly along with the generic OAuth2 settings.
Following these steps should resolve the issue where n8n reports that it cannot sign requests without an access token.
Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?
No comments yet.
Discussion
No comments yet.