From 56a1dd39e1916b677cd70e13ff38184119893f04 Mon Sep 17 00:00:00 2001 From: Mohammed Al Sahaf Date: Sun, 29 Sep 2024 14:13:18 +0300 Subject: [PATCH] doc: remove docs of deprecated directives (#415) --- src/docs/markdown/caddyfile/directives/tls.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/docs/markdown/caddyfile/directives/tls.md b/src/docs/markdown/caddyfile/directives/tls.md index c1c122d..1af809d 100644 --- a/src/docs/markdown/caddyfile/directives/tls.md +++ b/src/docs/markdown/caddyfile/directives/tls.md @@ -42,8 +42,6 @@ tls [internal|] | [ ] { client_auth { mode [request|require|verify_if_given|require_and_verify] trust_pool - trusted_leaf_cert - trusted_leaf_cert_file verifier } issuer [] @@ -140,16 +138,12 @@ Keep in mind that Let's Encrypt may send you emails about your certificate neari | verify_if_given | Ask clients for a certificate; allow even if there isn't one, but verify it if there is | | require_and_verify | Require clients to present a valid certificate that is verified | - Default: `require_and_verify` if any `trusted_ca_cert` or `trusted_leaf_cert` are provided; otherwise, `require`. + Default: `require_and_verify` if `trust_pool` module is provided; otherwise, `require`. - **trust_pool** configures the source of certificate authorities (CA) providing certificates against which to validate client certificates. The certificate authority used providing the pool of trusted certificates and the configuration within the segment depends on the configured source of trust pool module. The standard modules available in Caddy are [listed below](#trust-pool-providers). The full list of modules, including 3rd-party, is listed in the [`trust_pool` JSON documentation](/docs/json/apps/http/servers/tls_connection_policies/client_authentication/#trust_pool). - - **trusted_leaf_cert** is a base64 DER-encoded client leaf certificate to accept. - - - **trusted_leaf_cert_file** is a path to a PEM CA certificate file against which to validate client certificates. - Multiple `trusted_*` directives may be used to specify multiple CA or leaf certificates. Client certificates which are not listed as one of the leaf certificates or signed by any of the specified CAs will be rejected according to the **mode**. - **verifier** enables the use of a custom client certificate verifier module. These can perform custom client authentication checks, such as ensuring the certificate is not revoked.