5 ms·
“That means the root issue with renewal is still a problem, and we plan to address it in the short term much like our ancestors did: multiple redundant calendar
by Scubabear68 3y ago
“That means the root issue with renewal is still a problem, and we plan to address it in the short term much like our ancestors did: multiple redundant calendar alerts and a designated window to manually renew the certificates ourselves”.
- lijok 3y agoThe other day I was looking for a system where we can track recurring yearly/monthly/etc tasks (such as cert rotation) and get alerted a week before and on the day. 2~ hours into my search, contemplating building my own, someone pointed out we can just use a shared gsuite calendar. How the mind overcomplicates things sometimes..
- rustcleaner 3y ago[flagged]
- nimih 3y ago> When the Third Millennium Stasis kick off, basilisks on leashes, those are the intelligence treasure troves they will stripmine your optionality with. I don't know what all this means, but generally I think it's probably not too hard to deduce an org's schedule for certificate rotation by just looking at the expiration dates on those same certificates.
- lijok 3y agoI understand and somewhat agree with what you're saying. But good luck justifying that to the business.
- _joel 3y agoI'd probably spend the effort adding ssl expiration to the monitoring system for all the certs in use. Trigger then a month/week whatever before they're due to expire.
- rustcleaner 3y agoWe both got the downdoot simultaneously, someone didn't like our contributions. :^)
- deleted 3y ago[deleted]
- supriyo-biswas 3y agoUptime Kuma[1] has a certificate expiry notification feature. [1] https://github.com/louislam/uptime-kuma https://github.com/louislam/uptime-kuma
- eastbound 3y agoJira. Create an automation that clones tickets on due dates.
- j45 3y agoJira is really underrated for it's workflows and automations. Part of my love/hate relationship with JIRA was until the lightbulb that it's not supposed to work perfect out of the box because no two places are the same.
- mxuribe 3y agoThe org i work for at $dayjob is in the midst of a poorly-managed migration from Jira to Azure DevOps (ADO)...and I've had a tolerate/hate relationship with Jira for some years now...It often felt like it has too many distractions (what other people might call "bells and whistles"). So, when i recently started using ADO, i thought, eh, this is close enough to Jira, why all the fuss from some of my peers about missing Jira features and such? And, then I realized ADO lacks auto save (but Jira has it); freakin' auto save! Of all the things that i guess i miss from Jira; this is one of those seemingly minor features that i guess i grew to depend on while using Jira...So, yeah, i guess i hate Jira a little less. ;-)
- BuildTheRobots 3y agoHow can someone be hosting infrastructure without some form of monitoring and alerting framework? Domain and cert expiry (not just for your estate but for any of your dependencies) seems like the lowest of the hanging fruit checks to implement when setting that up.