generate_blob_shared_access_signature produces SAS incompatible with Azure when time format strings are not formatted correctly or datetime objects are not timezone aware #598
generate_blob_shared_access_signature produces SAS incompatible with Azure when time format strings are not formatted correctly or datetime objects are not timezone aware
blob SAS generation generate_blob_shared_access_signature
Issue relates to generate_blob_shared_access_signature, and by associate generate_blob etc
generate_blob_shared_access_signature produces SAS incompatible with Azure when time format strings are not formatted correctly or datetime objects are not timezone aware
blob SAS generation
generate_blob_shared_access_signature
Issue relates to
generate_blob_shared_access_signature
, and by associategenerate_blob
etcWhich version of the SDK was used?
azure-storage-blob
version1.5.0
What problem was encountered?
String time format in blob SAS generated by
generate_blob_shared_access_signature
causes Azure to reject the SAS and signature:datetime
object is given as start and end dates which is not timezone aware.YY-MM-DD:Thh:mm:ssZ
('%Y-%m-%dT%H:%M:%SZ'
).As a consumer of
generate_blob_shared_access_signature
I should not need to be aware of the idiosyncrasies of the Azure Blob SAS stuff.datetime
formats should just work however...Have you found a mitigation/solution?
Reparse all start and end times into a string of this format:
'%Y-%m-%dT%H:%M:%SZ'
as:Note: for table service, please post the issue here instead: https://github.com/Azure/azure-cosmosdb-python.