Skip to content

Commit 6bffd5c

Browse files
patriciasantaanapatriciasantaana
committed
api shield - partials
1 parent 366e60c commit 6bffd5c

File tree

3 files changed

+35
-32
lines changed

3 files changed

+35
-32
lines changed

‎src/content/partials/api-shield/mtls-create-rule.mdx‎

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,17 @@
33

44
---
55

6-
import { Steps } from "~/components"
6+
import { Steps, DashButton } from "~/components"
77

88
<Steps>
9-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
10-
2. Go to **SSL/TLS** > **Client Certificates**.
11-
3. Select **Create a mTLS rule**.
12-
4. In **Custom rules**, several rule parameters have already been filled in. Enter the URI path you want to protect in **Value**.
13-
5. (Optional) Add a `Hostname` field and enter the mTLS-enabled hostnames you wish to protect in **Value**.
14-
6. In **Choose action**, select `Block`.
15-
7. Select **Deploy** to make the rule active.
9+
1. In the Cloudflare dashboard, go to **Client Certificates** page.
10+
11+
<DashButton url="/?to=/:account/:zone/ssl-tls/client-certificates" />
12+
2. Select **Create a mTLS rule**.
13+
3. In **Custom rules**, several rule parameters have already been filled in. Enter the URI path you want to protect in **Value**.
14+
4. (Optional) Add a `Hostname` field and enter the mTLS-enabled hostnames you wish to protect in **Value**.
15+
5. In **Choose action**, select `Block`.
16+
6. Select **Deploy** to make the rule active.
1617
</Steps>
1718

1819
Once you have deployed your mTLS rule, any requests without a [valid client certificate](/ssl/client-certificates/) will be blocked.

‎src/content/partials/api-shield/sequence-custom-rules.mdx‎

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33

44
---
55

6-
import { Steps, Tabs, TabItem } from "~/components"
6+
import { Steps, Tabs, TabItem, DashButton } from "~/components"
77

88
<Tabs syncKey="dashNewNav">
99
<TabItem label="Old dashboard">
@@ -28,24 +28,25 @@ import { Steps, Tabs, TabItem } from "~/components"
2828
</TabItem>
2929
<TabItem label="New dashboard" icon="rocket">
3030
<Steps>
31-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
32-
2. Go to **Security** > **Security rules**.
33-
3. To create a new empty rule, select **Create rule** > **Custom rules**.
34-
4. Enter a descriptive name for the rule in **Rule name**.
35-
5. Under **When incoming requests match**, use the **Field** drop-down list to filter by **Sequences** and select from:
31+
1. In the Cloudflare dashboard, go to the **Security rules** page.
32+
33+
<DashButton url="/?to=/:account/:zone/security/security-rules" />
34+
2. To create a new empty rule, select **Create rule** > **Custom rules**.
35+
3. Enter a descriptive name for the rule in **Rule name**.
36+
4. Under **When incoming requests match**, use the **Field** drop-down list to filter by **Sequences** and select from:
3637
- Current Operation
3738
- Previous Operations
3839
- Elapsed time
39-
6. Under **Value**, select the edit icon to use Builder and build a sequence on the side panel.
40-
7. Under **Select a hostname for this sequence**, choose all or a specific hostname from the dropdown list. Optionally, you can use the search bar to search for a specific hostname.
41-
8. From the **Methods** dropdown list, choose all methods or a specific request method.
40+
5. Under **Value**, select the edit icon to use Builder and build a sequence on the side panel.
41+
6. Under **Select a hostname for this sequence**, choose all or a specific hostname from the dropdown list. Optionally, you can use the search bar to search for a specific hostname.
42+
7. From the **Methods** dropdown list, choose all methods or a specific request method.
4243
8. Select the checkbox for each endpoint in the order that you want them to appear in the sequence.
43-
8. Set the time to complete.
44-
9. Select **Save**.
45-
10. Under **Then take action**, select the rule action in the **Choose action** dropdown. For example, selecting *Block* tells Cloudflare to refuse requests that match the conditions you specified.
46-
11. (Optional) If you selected the *Block* action, you can configure a custom response.
47-
12. Under **Place at**, select the order of when the rule will fire.
48-
13. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
44+
9. Set the time to complete.
45+
10. Select **Save**.
46+
11. Under **Then take action**, select the rule action in the **Choose action** dropdown. For example, selecting *Block* tells Cloudflare to refuse requests that match the conditions you specified.
47+
12. (Optional) If you selected the *Block* action, you can configure a custom response.
48+
13. Under **Place at**, select the order of when the rule will fire.
49+
14. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
4950
</Steps>
5051
:::note
5152
The fields in the custom rule are populated as a grouped sequence based on the values that you entered on Builder.

‎src/content/partials/api-shield/set-up-session-identifiers.mdx‎

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
{}
33

44
---
5-
import { Steps, Tabs, TabItem } from "~/components"
5+
import { Steps, Tabs, TabItem, DashButton } from "~/components"
66

77
<Tabs syncKey="dashNewNav">
88
<TabItem label="Old dashboard">
@@ -23,19 +23,20 @@ import { Steps, Tabs, TabItem } from "~/components"
2323
</TabItem>
2424
<TabItem label="New dashboard" icon="rocket">
2525
<Steps>
26-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
27-
2. Go to **Security** > **Settings**
28-
3. Filter by **API abuse**.
29-
4. On **Session identifiers**, select **Configure session identifiers**.
30-
5. Select **Manage identifiers**.
31-
6. Choose the type of session identifier (cookie, HTTP header, or JWT claim).
26+
1. In the Cloudflare dashboard, go to the **Security Settings** page.
27+
28+
<DashButton url="/?to=/:account/:zone/security/settings" />
29+
2. Filter by **API abuse**.
30+
3. On **Session identifiers**, select **Configure session identifiers**.
31+
4. Select **Manage identifiers**.
32+
5. Choose the type of session identifier (cookie, HTTP header, or JWT claim).
3233
:::note
3334
The session identifier cookie must comply with RFC 6265. Otherwise, it will be rejected.
3435

3536
If you are using a JWT claim, choose the [Token Configuration](/api-shield/security/jwt-validation/api/#token-configurations) that will verify the JWT. Token Configurations are required to use JWT claims as session identifiers. Refer to [JWT Validation](/api-shield/security/jwt-validation/) for more information.
3637
:::
37-
7. Enter the name of the session identifier.
38-
8. Select **Save**.
38+
6. Enter the name of the session identifier.
39+
7. Select **Save**.
3940
</Steps>
4041
</TabItem>
4142
</Tabs>

0 commit comments

Comments
 (0)