You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the pki security engine to issue certificates, one can define a max_ttl parameter in the concerning role(s).
However, if you create a certificate and manually specify a ttl longer than the max_ttl value from the role, your value gets overwritten with the max value without showing any response or warning.
This might also happen when other parameters are overwritten by some set or defined limits.
Requested feature
It is completely understandable and correct to overwrite this value, if your_ttl > max_ttl, but a warning message or any kind of notification for this to happen would be highly appreciated when using the Web-GUI.
A response might be unpractical or even unnecessary when using the REST API, but a response from the Web-GUI and ideally from the CLI would definitely make sense imho.
The text was updated successfully, but these errors were encountered:
Thanks for this suggestion. This particular warning has been added (to the REST, CLI, and should turn up in the web-gui) here: #17073 , in our next release.
I'm referring to issue #6811.
Problem
When using the pki security engine to issue certificates, one can define a
max_ttl
parameter in the concerning role(s).However, if you create a certificate and manually specify a
ttl
longer than themax_ttl
value from the role, your value gets overwritten with the max value without showing any response or warning.This might also happen when other parameters are overwritten by some set or defined limits.
Requested feature
It is completely understandable and correct to overwrite this value, if
your_ttl > max_ttl
, but a warning message or any kind of notification for this to happen would be highly appreciated when using the Web-GUI.A response might be unpractical or even unnecessary when using the REST API, but a response from the Web-GUI and ideally from the CLI would definitely make sense imho.
The text was updated successfully, but these errors were encountered: