How to build Authorization Header for REST Requests in Black Pearl

[Rose Culture]

In the Black Pearl Docs, it explains that it used the AWS V2 protocol for building Authorization Headers to make RESTful requests for Black Pearl. There doesn't seem to be any examples or docs to show how these are built, or the key values that are needed to build the header.  For instance, here is Amazon AWS's:

Authorization: algorithm Credential=access key ID/credential scope, SignedHeaders=SignedHeaders, Signature=signature

What is the Black Pearl equivalent?  What are the values to construction the Authorization Header?

Thanks

[jeffbr]

Hi Rose, this page explains how to build a V2 authentication signature:

https://docs.aws.amazon.com/AmazonS3/latest/dev/S3_Authentication2.html

You can also look at the source code in our SDKs to see how Spectra built the V2 authentication signature:

https://developer.spectralogic.com/docs/

[jeffbr]

Rose, please also note that if you are trying to PUT or GET files from BlackPearl you should use our SDKs or RioBroker. BlackPearl does not support standard S3 PUT or GET because the file may need to come from or go to tape or Amazon Glacier, which can take minutes or hours. Standard S3 PUT and GET would time out in this case. You need use "Spectra S3", which consists of multiple API commands to transfer files. This is best done with our SDKs or with RioBroker.

https://developer.spectralogic.com/ds3/

https://developer.spectralogic.com/rio/