certimate-go / certimate-go/certimate

[Feature] 请求优化证书过期预警机制,使其能够根据证书的有效期动态计算或单独设置预警状态

Open
#1,426 1 comment 0 reactions 0 assignees View on GitHub
backlog enhancement
Dominant language
Go
Stars
9.3k
Forks
898
Avg merge
4d 5h
Merged PRs (30d)
8

Description

### Description / 功能描述

目前系统的过期预警采用全局固定天数配置。虽然当前版本已支持为单个证书配置独立的过期检测时间,但“SSL 证书管理”列表的状态显示依然强制按全局阈值计算。

建议提供以下改善方式之一:

动态按比例/阶梯计算(推荐):按证书总有效期的剩余百分比(如低于 25%)或按有效期区间自动匹配预警阶梯(如 >30 天证书提前 30 天预警,7-30 天证书提前 7 天预警,<7 天证书提前 1-2 天预警),无需繁琐配置。

继承单体设置(备选):“SSL 证书管理”列表的状态计算优先读取该证书配置的独立检测时间,未设置时再继承全局阈值。

### Motivation / 请求动机

消除短周期证书的视觉误报:随着 CAB Forum 推进短期证书规范,系统中常同时存在 90 天、30 天甚至 7 天等不同生命周期的证书。若全局阈值设为 30 天,短周期证书刚签发就会被错误标记为“临期”,产生大量干扰。

提高资产看板的真实性与专业度:使证书管理列表的状态能准确反映真实的运维风险,提升系统的自动化体验。

### Miscellaneous / 其他

_No response_

### Contribution / 贡献代码

- [ ] I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!

Contributor guide

Open the contributing guide

Research direction

Start by locating the SSL certificate management list and the status calculation that currently uses the global expiry threshold, then trace how per-certificate detection settings are stored and read. Confirm whether the implementation should use dynamic lifetime thresholds or inherit individual settings, and verify the result with certificates having 90-day, 30-day, and 7-day lifetimes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.