...
- Accept for both Shared Keys and Shared Access Signatures the respective configuration items:
- Both authentication methods
- Add to URL
- Resources
- container resource
- blob resource
- Example
https://<owner account specified by user>.blob.core.windows.net/<container specified by user>/<blob specified by user>
https://yade.blob.core.windows.net/yade/test.txt
- Add HTTPS headers:
x-ms-blob-type : BlockBlob
x-ms-date : <date of request>
x-ms-version : <version as specified by user>
- Add to URL
- Shared Key
- Add HTTPS authorization header:
Authorization : SharedKey <requester account specified by user>:<signature specified by user>
`
- Add HTTPS authorization header:
- Shared Access Signatures
- Add query parameters to URL for list operation
https://<owner account specified by user>.blob.core.windows.net/<container specified by user>/<blob specified by user>?<query parameters>
https://yade.blob.core.windows.net/yade/test.txt?restype=container&comp=list
- Add SAS token to URL:
https://<blob storage owner account specified by user>.blob.core.windows.net/<container specified by user>/<blob specified by user>?<SAS token specified by user>
- Add query parameters to URL for list operation
- Both authentication methods
- Adjust the YADE XSD Schema to allow configuration of any number of HTTP headers
- at a global level
- per profile
- on a per job basis by job/order parameters and when using the YADE standalone client by command line parameters.
- Delimitation
- The implementation is about integrating the above configuration items into HTTPS headers and query parameters.
- The implementation is not about developing a new data provider that is subject to a separate feature request.
...