Updating docs to indicate correct Authorization Header for Signed URL requests

[kellydunn]

While attempting to integrate our backend with Cloudflare Stream, I was consistently receiving the following error when supplying the "X-Auth-Key: ${API-KEY}" header as the docs indicate:

{"success":false,"errors":[{"code":10000,"message":"Authentication error"}]}

However, when supplying the same API_KEY as an Authorization: Bearer ${API_KEY} header, I'm able to get a successful request.

This PR updates the docs to reflect this.

[renandincer]

Hey @kellydunn: Cloudflare API has two authentication methods: API Keys and API Tokens.

You either need to specify X-Auth-Email and X-Auth-Key headers where auth key is your global API key, or a Authorization header with a API Token. The reason you might be getting authentication errors could be because you are using an API Token where a Global API Key is expected.

Here's the page where some differences between tokens and keys are documented: https://support.cloudflare.com/hc/en-us/articles/200167836-Managing-API-Tokens-and-Keys

New developers on Cloudflare seem to use API Tokens rather than Keys so I think we should move all examples in the Stream docs to use Tokens.

[adamschwartz]

@ispivey @renandincer should this be closed?

[kellydunn]

New developers on Cloudflare seem to use API Tokens rather than Keys so I think we should move all examples in the Stream docs to use Tokens.

Word, yeah -- we currently enjoy segmenting access to third-party APIs in our SOA/microservice Architecture by creating Service Specific Access Tokens, not just for cloudflare, but for other services as well. I'd imagine folks would definitely want to follow similar patterns if they wanted to separate access on a service by service level.

[renandincer]

@adamschwartz I'll push up a change making all examples use auth tokens, rather than auth keys to avoid confusion. Please keep this open for a few days until I get to it.

[renandincer]

Opened #149 to make this change across the entire Stream docs

[adamschwartz]

@renandincer Should we close this then?

[renandincer]

Yep! Let's discuss on #149!

[cloudflare-workers-and-pages]

Deploying cloudflare-docs with    Cloudflare Pages

Latest commit:	5a4b7f8
Status:	✅  Deploy successful!
Preview URL:	https://35d18397.cloudflare-docs-7ou.pages.dev

View logs

[github-actions]

Files with changes (up to 15)

Original Link	Updated Link