ナビ付きでトピックを開く

 

Authentication (CDN Object Storage)

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
CDN Object StorageThis service was discontinued on 11/12/2018. This storage solution is designed to store content on behalf of the Media Ingest feature.

Media Ingest and CDN Object Storage underwent end-of-life on 11/12/2018. Content may no longer be streamed via Media Ingest and content uploaded by your encoder to CDN Object Storage is no longer available. This article is still available in order to provide assistance while you migrate to a new streaming workflow.

Authentication, which is only required when uploading and deleting content from CDN Object Storage, may be performed by submitting credentials (i.e., an access and secret key pair) with each request to upload or delete content.

Unauthenticated requests to upload or delete content will return a 401 Unauthorized response.

An access and secret key pair authenticates requests to manage content within any bucket.

A media player may retrieve content without authenticating to the CDN Object Storage service.

Access and Secret Key Pairs

Content management on CDN Object Storage requires authentication via an access and secret key pair.

Key information:

ClosedTo add an access and secret key pair
  1. Navigate to the Object Storage page.

  2. Verify that either the primary or backup key is currently unassigned.

    Delete a key pair if both key pairs are currently active.

  3. Click + Add Key to generate a random access and secret key.
ClosedTo delete an access and secret key pair
  1. Navigate to the Object Storage page.

  2. Verify that both key pairs are active.

    Add a key pair if only one key pair has been defined.

  3. Click Delete next to the access and secret pair that should be deleted.
  4. Confirm key deletion by clicking Delete Key.

Authenticating Requests

This section is only applicable when manually uploading or deleting content from CDN Object Storage. When configured properly, an encoder's upload and delete requests are automatically authenticated.

Requests to upload or delete content to CDN Object Storage must be authenticated. Information on how to authenticate HTTPS requests to CDN Object Storage is provided below.

Requests to playback content do not require authentication. However, security may be applied to content stored on CDN Object Storage.

Request

Authenticate a POST, PUT, or DELETE request by performing the following steps:

  1. Apply Base64-encoding to the following value:

    AccessKeyReplace this variable with an access key that corresponds to the CDN Object Storage location (e.g., TEB) where the bucket is stored. :SecretKeyReplace this variable with a secret key that corresponds to the specified access key.

  2. Include an Authorization header with the request. Set it to the following value:

    Basic Base64-Encoded-Key-PairReplace this variable with the Base64-encoded value generated in the previous step.

Response

The response varies according to whether the request was successfully carried out.

Response Code Description

204 No Content

Indicates that the specified asset was uploaded or deleted.

401 Unauthorized

Indicates that the request was unauthorized and the asset was not uploaded or deleted.

Troubleshooting:

  • Verify that the Authorization header was included in the request.

403 Forbidden

Indicates that the request was unauthorized and the asset was not uploaded or deleted.

Troubleshooting:

  • Review and adjust the value assigned to the Authorization header.
    • Verify that the access and secret key pair is valid.

    • Verify that Base64-encoding has been applied to the access and secret key pair.

      A colon must delimit an access key from a secret key.
More Information