You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Juliehzl opened this issue
Aug 13, 2020
· 2 comments
Assignees
Labels
bugThis issue requires a change to an existing behavior in the product in order to be resolved.ClientThis issue points to a problem in the data-plane of the library.StorageStorage Service (Queues, Blobs, Files)
Describe the bug
A clear and concise description of what the bug is.
When specify permission with string, it passes the permission string to _str as shown here:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugThis issue requires a change to an existing behavior in the product in order to be resolved.ClientThis issue points to a problem in the data-plane of the library.StorageStorage Service (Queues, Blobs, Files)
Describe the bug
A clear and concise description of what the bug is.
When specify permission with string, it passes the permission string to _str as shown here:
azure-sdk-for-python/sdk/storage/azure-storage-blob/azure/storage/blob/_models.py
Line 930 in 1216acf
but what we expect is that it should be format with the following method:
azure-sdk-for-python/sdk/storage/azure-storage-blob/azure/storage/blob/_models.py
Lines 899 to 904 in 1216acf
If the permission string sequence changes, it will cause signed signature change and authentication failure.
Removing this line could fix it.
azure-sdk-for-python/sdk/storage/azure-storage-blob/azure/storage/blob/_models.py
Line 930 in 1216acf
Same for other sas permissions.
To Reproduce
Steps to reproduce the behavior:
but if you are using
rwdl
, it will work.Expected behavior
A clear and concise description of what you expected to happen.
Authentication failed.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: