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
Description:
When using an offline Root CA in HashiCorp Vault, it's not currently possible to revoke an intermediate CA properly, as there is no built-in API endpoint to upload a signed Certificate Revocation List (CRL). The offline Root CA model means that Vault cannot automatically sign and upload CRLs without manual intervention or external plugins like the ACME plugin. This makes it challenging to maintain CRL distribution and ensure proper revocation processes for Intermediate CAs.
Proposed Solution:
I suggest creating a new API endpoint that would allow users to manually upload a pre-signed CRL. This would facilitate better support for offline Root CAs without relying on external tools or plugins. By adding this feature, administrators could manually upload the signed CRL from their offline Root CA, which would then be distributed by Vault for certificate revocation.
The text was updated successfully, but these errors were encountered:
Description:
When using an offline Root CA in HashiCorp Vault, it's not currently possible to revoke an intermediate CA properly, as there is no built-in API endpoint to upload a signed Certificate Revocation List (CRL). The offline Root CA model means that Vault cannot automatically sign and upload CRLs without manual intervention or external plugins like the ACME plugin. This makes it challenging to maintain CRL distribution and ensure proper revocation processes for Intermediate CAs.
Proposed Solution:
I suggest creating a new API endpoint that would allow users to manually upload a pre-signed CRL. This would facilitate better support for offline Root CAs without relying on external tools or plugins. By adding this feature, administrators could manually upload the signed CRL from their offline Root CA, which would then be distributed by Vault for certificate revocation.
The text was updated successfully, but these errors were encountered: