@@ -81,6 +81,48 @@ Additionally certificates may be reloaded by setting the below configuration.
8181 Accepts a [ duration string] ( https://pkg.go.dev/time#ParseDuration ) ,
8282 valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".
8383
84+ ## CRL (Certificate Revocation List) Configuration
85+
86+ CRL checking can be enabled to verify that peer certificates have not been
87+ revoked. When a CRL is configured, every peer certificate presented during
88+ the TLS handshake is checked against the revocation list. If a revoked
89+ certificate is found, the TLS handshake is aborted.
90+
91+ - ` crl_file ` : Path to a CRL file in PEM format. (optional)
92+
93+ - ` crl_reload_interval ` (optional): Specifies the duration after which the CRL file will be
94+ reloaded from disk. If not set, the CRL is loaded once at startup and never refreshed.
95+ Accepts a [ duration string] ( https://pkg.go.dev/time#ParseDuration ) ,
96+ valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".
97+
98+ Example (client with CRL checking):
99+ ``` yaml
100+ exporters :
101+ otlp :
102+ endpoint : myserver.local:55690
103+ tls :
104+ ca_file : ca.crt
105+ cert_file : client.crt
106+ key_file : client.key
107+ crl_file : revoked-certs.pem
108+ crl_reload_interval : 1h
109+ ` ` `
110+
111+ Example (server with CRL checking):
112+ ` ` ` yaml
113+ receivers :
114+ otlp :
115+ protocols :
116+ grpc :
117+ endpoint : mysite.local:55690
118+ tls :
119+ cert_file : server.crt
120+ key_file : server.key
121+ client_ca_file : client-ca.crt
122+ crl_file : revoked-certs.pem
123+ crl_reload_interval : 30m
124+ ` ` `
125+
84126How TLS/mTLS is configured depends on whether configuring the client or server.
85127See below for examples.
86128
0 commit comments