Updating docs to indicate correct Authorization Header for Signed URL requests#2
Updating docs to indicate correct Authorization Header for Signed URL requests#2kellydunn wants to merge 1 commit intocloudflare:masterfrom
Conversation
|
Hey @kellydunn: Cloudflare API has two authentication methods: API Keys and API Tokens. You either need to specify 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. |
|
@ispivey @renandincer should this be closed? |
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. |
|
@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. |
|
Opened #149 to make this change across the entire Stream docs |
|
@renandincer Should we close this then? |
|
Yep! Let's discuss on #149! |
Deploying cloudflare-docs with
|
| Latest commit: |
1d16bbe
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://359b3f44.cloudflare-docs-7ou.pages.dev |
Update short-lived-certificates.md
|
Files with changes (up to 15)
|
* [Chore] Expand ignore list #2 * Update language
* Add placeholders for new folder and pages and fill in frontmatter * Add outline for index.mdx and fill in TLS background info * Apply suggestion: Reword intro to TLS building blocks Co-authored-by: Peter Wu <peter@lekensteyn.nl> * Fix typo and reword index.mdx meta description * Improve parallelism, refine text, and link out to TLS handshake LC * Fill in hybrid key agreement section * Complete visitor-to-cloudflare intro paragraph * Add mermaid digram for connections and reword #2 * Fix Internet capitalization Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> * Rename file, fill in, and link to pqc-support * Fix capitalization and fill in Intenal connections section * Fill in Cf to origin and review titles and headings * Fix missing hyphen and touch up pqc-to-origin description * Add split ClientHello and HRR workaround to pqc-to-origin * Add setup instructions to pqc-to-origin * Apply suggestion from code review Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Luke Valenta <lvalenta@cloudflare.com> Co-authored-by: Suleman Ahmad <36677672+SulemanAhmadd@users.noreply.github.com> * Replace store by harvest, adjust RFC link cf Style Guide, and split long paragarph * Add reference to PQ signatures and link out to blog * Fix origin server section to use fork and bssl for both cases * Add link to Cloudflare Radar Co-authored-by: Luke Valenta <lvalenta@cloudflare.com> * Text review and move link to Radar higher up in the page * Simplify origin server instructions to use BoringSSL instead of fork Co-authored-by: Suleman Ahmad <36677672+SulemanAhmadd@users.noreply.github.com> * Overall text review and remove previous origin instructions * Apply suggestion from code review Co-authored-by: Jun Lee <junlee@cloudflare.com> --------- Co-authored-by: Peter Wu <peter@lekensteyn.nl> Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> Co-authored-by: Luke Valenta <lvalenta@cloudflare.com> Co-authored-by: Suleman Ahmad <36677672+SulemanAhmadd@users.noreply.github.com> Co-authored-by: Jun Lee <junlee@cloudflare.com>
* Add placeholders for new folder and pages and fill in frontmatter * Add outline for index.mdx and fill in TLS background info * Apply suggestion: Reword intro to TLS building blocks Co-authored-by: Peter Wu <peter@lekensteyn.nl> * Fix typo and reword index.mdx meta description * Improve parallelism, refine text, and link out to TLS handshake LC * Fill in hybrid key agreement section * Complete visitor-to-cloudflare intro paragraph * Add mermaid digram for connections and reword #2 * Fix Internet capitalization Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> * Rename file, fill in, and link to pqc-support * Fix capitalization and fill in Intenal connections section * Fill in Cf to origin and review titles and headings * Fix missing hyphen and touch up pqc-to-origin description * Add split ClientHello and HRR workaround to pqc-to-origin * Add setup instructions to pqc-to-origin * Apply suggestion from code review Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Luke Valenta <lvalenta@cloudflare.com> Co-authored-by: Suleman Ahmad <36677672+SulemanAhmadd@users.noreply.github.com> * Replace store by harvest, adjust RFC link cf Style Guide, and split long paragarph * Add reference to PQ signatures and link out to blog * Fix origin server section to use fork and bssl for both cases * Add link to Cloudflare Radar Co-authored-by: Luke Valenta <lvalenta@cloudflare.com> * Text review and move link to Radar higher up in the page * Simplify origin server instructions to use BoringSSL instead of fork Co-authored-by: Suleman Ahmad <36677672+SulemanAhmadd@users.noreply.github.com> * Overall text review and remove previous origin instructions * Apply suggestion from code review Co-authored-by: Jun Lee <junlee@cloudflare.com> --------- Co-authored-by: Peter Wu <peter@lekensteyn.nl> Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> Co-authored-by: Luke Valenta <lvalenta@cloudflare.com> Co-authored-by: Suleman Ahmad <36677672+SulemanAhmadd@users.noreply.github.com> Co-authored-by: Jun Lee <junlee@cloudflare.com>
* [Workers AI] Models update * fix logic * fix deprecation logic #2 * Update changelog for EmbeddingGemma * Update src/content/changelog/workers-ai/2025-09-05-embeddinggemma.mdx Co-authored-by: Anni Wang <54481763+aninibread@users.noreply.github.com> --------- Co-authored-by: kodster28 <kody@cloudflare.com> Co-authored-by: Anni Wang <54481763+aninibread@users.noreply.github.com>
add note #2 hover to REST API limit as well
* [Browser Rendering] Hover notes on limits * Update src/content/docs/browser-rendering/limits.mdx Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> * Update src/content/docs/browser-rendering/limits.mdx Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> * Update src/content/docs/browser-rendering/limits.mdx Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> * Update limits.mdx add note #2 hover to REST API limit as well --------- Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> Co-authored-by: Kathy <153706637+kathayl@users.noreply.github.com>
---
pcx_content_type: how-to
title: DLP profiles
sidebar:
order: 3
label: Configure DLP profiles
---
import { Render } from "~/components";
A DLP profile is a collection of regular expressions and [detection entries](/cloudflare-one/data-loss-prevention/detection-entries/) that define the data patterns you want to detect. Cloudflare DLP provides predefined profiles for common detections, or you can build custom DLP profiles specific to your data, organization, and risk tolerance.
## Configure a predefined profile
<Render
file="data-loss-prevention/predefined-profile"
product="cloudflare-one"
/>
You can now use this profile in a [DLP policy](/cloudflare-one/data-loss-prevention/dlp-policies/cloudflare#2-create-a-dlp-policy) or [CASB integration](/cloudflare-one/cloud-and-saas-findings/casb-dlp/).
## Build a custom profile
<Render file="data-loss-prevention/custom-profile" product="cloudflare-one" />
You can now use this profile in a [DLP policy](/cloudflare-one/data-loss-prevention/dlp-policies/cloudflare#2-create-a-dlp-policy) or [CASB integration](/cloudflare-one/cloud-and-saas-findings/casb-dlp/).
* [Browser Rendering] Hover notes on limits * Update src/content/docs/browser-rendering/limits.mdx Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> * Update src/content/docs/browser-rendering/limits.mdx Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> * Update src/content/docs/browser-rendering/limits.mdx Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> * Update limits.mdx add note #2 hover to REST API limit as well --------- Co-authored-by: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com> Co-authored-by: Kathy <153706637+kathayl@users.noreply.github.com>
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:However, when supplying the same
API_KEYas anAuthorization: Bearer ${API_KEY}header, I'm able to get a successful request.This PR updates the docs to reflect this.