Skip to content

Commit 5621e07

Browse files
more wording
1 parent dd929a2 commit 5621e07

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/content/docs/cloudflare-one/identity/devices/warp-client-checks/client-certificate.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar:
77

88
import { Details, Render, TabItem, Tabs } from "~/components";
99

10-
The Client Certificate device posture attribute checks if the device has a valid certificate signed by a trusted certificate authority (CA). The posture check can be used in Gateway and Access policies to ensure that the user is connecting from a managed device.
10+
The Client Certificate device posture attribute checks if the device has a valid client certificate signed by a trusted certificate authority (CA). The trusted CA is the signing certifiate you upload to Cloudflare. The client certificate posture check can be used in Gateway and Access policies to ensure that the user is connecting from a managed device.
1111

1212
<Details header="Feature availability">
1313

@@ -31,7 +31,7 @@ The Client Certificate device posture attribute checks if the device has a valid
3131

3232
- A CA that issues client certificates for your devices. WARP does not evaluate the certificate trust chain; this needs to be the issuing certificate.
3333

34-
:::caution[Upload the signing certificate that directly issued the client certificate]
34+
:::note[Upload the signing certificate that directly issued the client certificate]
3535

3636
When uploading a certificate to use in posture checks, Cloudflare does not differentiate between root and intermediate certificates. You must upload the actual signing certificate – the one that directly signed the client certificate.
3737

0 commit comments

Comments
 (0)