Upload Credential

Place the upload credential in the request form; parameter name: token.

The three underlying data sources for constructing the upload credential are as follows:

• Upload Policy Data (putPolicy)
  Upload Policy Data are a set of configuration settings supplied during the resource upload. With this set of configuration information, CDNetworks Object Storage can understand a user’s upload requirements: What resources he/she will upload, to which bucket he/she will upload, whether the upload result is callback notification or using redirection, whether the content of the feedback information needs to be set, and the end of the validity period of authorized upload, so on and so forth.
• Security Key (SecretKey)
  Please obtain the SK from the Object Storage storage platform key administrator.
• Access Key (AccessKey)
  Please obtain the AK from the Object Storage storage platform key administrator.

The upload credential uploadToken is the result of a complex signature calculation based on the three underlying data sources. By verifying the upload credential, we can ensure that illegal upload requests are blocked and illegal intrusions are prevented.

Upload Policy Data

Data Format

     {
      "scope": "<bucket string>",
      "deadline": "<deadline string>",
      "saveKey": "<saveKey string>"
      "returnUrl": "<returnUrl string>",
      "returnBody": "<returnBody string>",
      "overwrite": "<overwrite int>",
      "fsizeLimit": "<fsizeLimit long>",
      "callbackUrl": "<callbackUrl string>",
      "callbackBody": "<callbackBody string>",
      "persistentOps": "<persistentOps string>",
      "persistentNotifyUrl": "<persistentNotifyUrl string>"
      "contentDetect": "<contentDetctstring>"
      "detectNotifyURL": "<detectNotifyURL string>"
      "detectNotifyRule":"<detectNotifyRule>"
      "separate": "<separate int>"
    }

Format Descriptions

Note:

1. Please complete setting the persistentNotifyUrl field when setting the persistenOps field. The platform will notify you of the result of instruction processing by calling the URL set in the persistentNotifyUrl field. For details, see the Notification Data Content Description.
2. Use the upload processing mechanism. When setting the persistenOps field, the instruction parameter saveas is required and the key may not be the same as that of the original file. Otherwise, a 401 will be returned with the prompt message of “The Persistent File Already Exists”
3. The file naming priority is as follows: The key of Scope > saveKey > form key > name of the original file

​​Upload Credential Generation Algorithm​

1. Build the upload policy
Use the JSON format to encapsulate some information of the uploaded file putPolicy

     {
      "scope": "<bucket string>",
      "deadline": "<deadline string>",
      "returnBody": "<returnBody string>",
      "overwrite": "<overwrite int>",
      "fsizeLimit": "<fsizeLimit long>",
      "returnUrl": "<returnUrl string>"
    }

2. Upload Policy For URL-Safe Base64 Codes

Perform URL-Safe Base64 Encoding for putPolicy to obtain encodePutPolicy

encodePutPolicy = urlsafe_base64_encode(putPolicy)

3. HMAC-SHA1 Signature Generation
Use SecretKey to provide HMAC-SHA1 signature for encodePutPolicy to obtain Sign

Sign = hmac_sha1(encodePutPolicy, "<SecretKey>")

4. URL-Safe Base64 Encoded Signature Data
Perform URL-Safe Base64 Encoding for the signature data Sign to obtain encodedSign

encodeSign = urlsafe_base64_encode(Sign)

5. Generate the Upload Credential
Join AccessKey, encodedSign and encodeputPolicy together using : to obtain the upload credential uploadToken

uploadToken = AccessKey:encodedSign:encodePutPolicy