# Certificate revocation via CLR or OCSP **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [November 4, 2017, 4:17pm UTC](https://discuss.elastic.co/t/certificate-revocation-via-clr-or-ocsp/106382 "2017-11-04T16:17:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![9nativ](https://avatars.discourse-cdn.com/v4/letter/9/b782af/32.png) [@9nativ](https://discuss.elastic.co/u/9nativ)\ **Post date:** [November 4, 2017, 4:17pm UTC](https://discuss.elastic.co/t/certificate-revocation-via-clr-or-ocsp/106382/1 "2017-11-04T16:17:54Z")
Hi, We are using Filebeat (version 5.4.2) to ship our customer's logs to logstash servers and we are testing the process of server certificate revocation. As Filebeat using golang TLS stack, we noticed that Filebeat implemeation isn't checking for certificate revocation via CLR or OCSP. Are you aware of it, can we ask to support the implemeation for CLR or OCSP validation? ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [November 6, 2017, 10:45am UTC](https://discuss.elastic.co/t/certificate-revocation-via-clr-or-ocsp/106382/2 "2017-11-06T10:45:29Z")
Please open an issue on [https://github.com/elastic/beats/issues](https://github.com/elastic/beats/issues) . While beats is using the golang TLS stack, CLR/OCSP seem not to be available out of the box. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 4, 2017, 10:45am UTC](https://discuss.elastic.co/t/certificate-revocation-via-clr-or-ocsp/106382/3 "2017-12-04T10:45:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.