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
Describe the bug
Today, in the Airlock processor, we use the SAS token for the source blob in order to copy the blob.
There might be an option to copy the containers without issuing a sas token. This issue is to see if possible and fix if it is.
The text was updated successfully, but these errors were encountered:
It looks like this isn't possible. Despite some operations are allowed to use AD AuthN, copy between accounts doesn't work with python sdk or azure cli. The error from azure-cli:
Server failed to authenticate the request. Please refer to the information in the www-authenticate header.
RequestId:3ff69ae2-501e-002d-7cc1-a0e67a000000
Time:2022-07-26T07:29:19.2951512Z
ErrorCode:CannotVerifyCopySource
Surprisingly it DOES work when using azcopy. I've verified the identity used has no permission to get the account keys (and hence can't generate a SAS internally), and that it doesn't download the blob and re-uploads it to the destination.
tamirkamara
changed the title
Remove redundant sas token when copying blobs
Copy blobs without sas tokens
Aug 2, 2022
Describe the bug
Today, in the Airlock processor, we use the SAS token for the source blob in order to copy the blob.
There might be an option to copy the containers without issuing a sas token. This issue is to see if possible and fix if it is.
The text was updated successfully, but these errors were encountered: