From 97755981ebf89ddb2674a72c53d0b6f92f3c93ff Mon Sep 17 00:00:00 2001 From: Akhil Mohan Date: Wed, 25 Jun 2025 14:43:01 +0530 Subject: [PATCH] Update docs/documentation/platform/identities/tls-cert-auth.mdx Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com> --- docs/documentation/platform/identities/tls-cert-auth.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/documentation/platform/identities/tls-cert-auth.mdx b/docs/documentation/platform/identities/tls-cert-auth.mdx index be309bf41..c4d5556f4 100644 --- a/docs/documentation/platform/identities/tls-cert-auth.mdx +++ b/docs/documentation/platform/identities/tls-cert-auth.mdx @@ -33,7 +33,7 @@ At a high level, Infisical authenticates the client's TLS Certificate by verifyi To be more specific: -1. The client sends a TLS request with the client certificate to Infisical at the `/api/v1/auth/tls-cert-auth/login endpoint.` +1. The client sends a TLS request with the client certificate to Infisical at the `/api/v1/auth/tls-cert-auth/login` endpoint. 2. Infisical verifies the incoming request using the provided CA certificate. 3. Infisical checks the user's properties against set criteria such as Allowed Common Names. 4. If all checks pass, Infisical returns a short-lived access token that the client can use to make authenticated requests to the Infisical API.