-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure SAS authorization fails with <AuthenticationErrorDetail>Signature fields not well formed.
#910
Comments
Hi @wjones127, thanks for looking into this so quickly! Here's my access pattern:
I also tried some aliases for "account_name" and "sas_token" found here |
@xbrianh - could you confirm really quick. I think we are expecting the sas token in the form as it would be if generated in the Storage Explorer. I that how you are passing it in? |
Same issue with sas token generated in Storage Explorer. |
I'm not able to reproduce with Azurite, so the SAS token signature might not be validated there in full. We should test against the real API. |
I was able to reproduce the error against a real account. Will have to do some digging, as we tested this quite throughly when integrating it into object store. |
I faced the same problem with SAS tokens generated by Azure Portal or Azure Storage explorer. Any updates on this? |
Environment
Delta-rs version: 0.6.2
Binding: python
Using a sas token to access a deltalake on AzureStorage throws an authorization error. The sas token was verified out of band.
Interestingly, the thrown error provides a failed blob url. Comparing this with a working url, the sas fields in the failed url are url-quoted. For instance:
The text was updated successfully, but these errors were encountered: