# SSL Certificate Durations

**URL:** <https://community.icinga.com/t/ssl-certificate-durations/415>\
**Category:** Icinga 2\
**Tags:** certificates, tls\
**Created:** [February 19, 2019, 6:50pm UTC](https://community.icinga.com/t/ssl-certificate-durations/415 "2019-02-19T18:50:33Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dnsmichi](https://community.icinga.com/user_avatar/community.icinga.com/dnsmichi/32/7721_2.png) [@dnsmichi](https://community.icinga.com/u/dnsmichi)\
**Post date:** [February 20, 2019, 8:12am UTC](https://community.icinga.com/t/ssl-certificate-durations/415/3 "2019-02-20T08:12:48Z")

</div>

Hi,

that’s a hardcoded value following typical recommendations. AFAIK thanks to RHEL5 boundaries we’ve lowered this from 30 to 15 years. That was before we’ve invented the CA proxy and automated certificate renewal by clients who trust each other already.

If you really need a different duration, you need to manage the certificates outside of Icinga and generate your own. There’s a discussion topic for this here: [Own CA for Icinga Cluster/API communication?](https://community.icinga.com/t/own-ca-for-icinga-cluster-api-communication/243)

Cheers,  
Michael

---

_[View the full topic](https://community.icinga.com/t/ssl-certificate-durations/415)._
