Salt does not allow custom validation dates to be specified for new X509 certificates #53148
Labels
Confirmed
Salt engineer has confirmed bug/feature - often including a MCVE
Execution-Module
Feature
new functionality including changes to functionality and code refactors, etc.
State-Module
Milestone
Comments
twangboy
added
Execution-Module
Feature
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
sagetherage
added
the
Confirmed
|
Thank you for updating this issue. It is no longer marked as stale. |
|
Fixed in #53149 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of Issue/Question
The current Salt x509 support issues certificates based on the current timestamp when the module is invoked as the starting date ("not_before") and with the expiration date ("not_after") being calculated based on a number of validity dates.
I would like to make it possible to issue certificates with well-defined expiration dates, however when passing dates as
not_beforeandnot_afterattributes for the X509 state, these attributes are ignored.Setup
(Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)
Steps to Reproduce Issue
(Include debug logs if possible and relevant.)
Versions Report
(Provided by running
salt --versions-report. Please also mention any differences in master/minion versions.)The text was updated successfully, but these errors were encountered: