Custome Storage account failing with AuthorizationFailure(statuscode= 403)
soumya-222 opened this issue · comments
Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the Azurite was used?
3.27
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
DockerHub
What's the Node.js version?
18.18
What problem was encountered?
while using custom account getting 403 unauthorized error
env:
-
name: AZURITE_ACCOUNTS
value: account1:ZGV2c3RvcmVhY2NvdW50Mw==getting 403 what is the proper value of key i feel key value needs to be proper i have provided some random base64 value in case of devstoreaccount1 it is working but with custom account saying
AuthorizationFailure Server failed to authenticate the request. Make sure the value of the Authorization header is formed correctly including the signature. RequestId:775363f9-104c-4e1a-8760-c272ea109e55 Time:2024-02-05T18:16:23.918Z "
Steps to reproduce the issue?
1)Get azurite using DockerHub
2) Deployed in a kubernetes env
3)used env variable for custome accounts
env:
-
name: AZURITE_ACCOUNTS
value: account1:ZGV2c3RvcmVhY2NvdW50Mw==while trying use the blob storage liek upload and downlead getting
AuthorizationFailure Server failed to authenticate the request. Make sure the value of the Authorization header is formed correctly including the signature. RequestId:775363f9-104c-4e1a-8760-c272ea109e55 Time:2024-02-05T18:16:23.918Z "
If possible, please provide the debug log using the -d parameter, replacing <pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
-d "<pathtodebuglog>"
Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
@EmmaZhu
can you please look the issue and help me to resolve the issue .