|
2 | 2 | {} |
3 | 3 |
|
4 | 4 | --- |
5 | | -import { Steps } from "~/components" |
| 5 | +import { Steps, Tabs, TabItem } from "~/components" |
6 | 6 |
|
7 | | -<Steps> |
8 | | -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain. |
9 | | -2. Go to **Security** > **API Shield**. |
10 | | -3. Select **Settings**. |
11 | | -4. On **Endpoint settings**, select **Manage identifiers**. |
12 | | -5. Choose the type of session identifier (cookie, HTTP header, or JWT claim). |
13 | | - :::note |
14 | | - The session identifier cookie must comply with RFC 6265. Otherwise, it will be rejected. |
| 7 | +<Tabs syncKey="dashNewNav"> |
| 8 | + <TabItem label="Old dashboard"> |
| 9 | + <Steps> |
| 10 | + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain. |
| 11 | + 2. Go to **Security** > **API Shield**. |
| 12 | + 3. Select **Settings**. |
| 13 | + 4. On **Endpoint settings**, select **Manage identifiers**. |
| 14 | + 5. Choose the type of session identifier (cookie, HTTP header, or JWT claim). |
| 15 | + :::note |
| 16 | + The session identifier cookie must comply with RFC 6265. Otherwise, it will be rejected. |
15 | 17 |
|
16 | | - 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. |
17 | | - ::: |
18 | | -6. Enter the name of the session identifier. |
19 | | -7. Select **Save**. |
20 | | -</Steps> |
| 18 | + 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. |
| 19 | + ::: |
| 20 | + 6. Enter the name of the session identifier. |
| 21 | + 7. Select **Save**. |
| 22 | + </Steps> |
| 23 | + </TabItem> |
| 24 | + <TabItem label="New dashboard" icon="rocket"> |
| 25 | + <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). |
| 32 | + :::note |
| 33 | + The session identifier cookie must comply with RFC 6265. Otherwise, it will be rejected. |
| 34 | + |
| 35 | + 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. |
| 36 | + ::: |
| 37 | + 7. Enter the name of the session identifier. |
| 38 | + 8. Select **Save**. |
| 39 | + </Steps> |
| 40 | + </TabItem> |
| 41 | +</Tabs> |
21 | 42 |
|
22 | 43 | After setting up session identifiers and allowing some time for Cloudflare to learn your traffic patterns, you can view your per endpoint and per session rate limiting recommendations, as well as enforce per endpoint and per session rate limits by creating new rules. Session identifiers will allow you to view API Discovery results from session ID-based discovery and session traffic patterns in Sequence Analytics. |
0 commit comments