Describe the problem/error/question
I am able to successfully use HTTP node when reading or writing to my Azure Blob Storage however in order to do so, I am putting my Shared Access Signature (SAS) sig directly in the URI. Obviously, I don’t want this so I have been trying to use n8n Generic Credentials and just pass the sig as the authentication however I only get failures.
Sample PUT Query:
https://[blobname].blob.core.windows.net/[container]/test.csv?sv=2023-01-03&ss=btqf&srt=sco&st=2025-01-13T17%3A04%3A10Z&se=2025-03-14T17%3A04%3A00Z&sp=rwdftlacup&sig=[SAS]
Headers:
Content-Type: “text/csv”
x-ms-blob-type: “BlockBlob”
To repeat, this HTTP node works 100% of the time if I embed the sig directly in URI. Through credentials it does not.
What is the error message (if any)?
Forbidden - perhaps check your credentials?
AuthenticationFailedServer failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. Signature fields not well formed.
Please share your workflow
No need to share the workflow. This is repeatable with any azure blob and just HTTP node.
Information on your n8n setup
- n8n version: 1.75.2
- Database: None
- n8n EXECUTIONS_PROCESS setting: Main
- Running n8n via: n8n cloud
- Operating system: MacOS
Additional
I did find that there is a community node for Azure Blob but I do not want to use. This should work with Query Auth and its not.