[RFE] add an action to set up an internal root ca to be used for pre-intermediate-CSR testing iterations

Bug #1776976 reported by Dmitrii Shcherbakov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vault-charm
Triaged
Wishlist
Unassigned

Bug Description

During on-site deployments there are cases where several deployment iterations are required.

As vault is normally a part of a single model along with OpenStack services, we need to take it down along with everything else which leads to loss of private keys and intermediate CA certs.

In order to do several test iterations we need to either work with a dummy easyrsa-based CA and sign CSRs from vault or, alternatively, use vault as a root CA.

https://www.vaultproject.io/api/secret/pki/index.html#generate-root

This is a feature request to implement an action to generate a root CA and logic around it for switching to an intermediate ca at a later point and regenerating already issued certificates.

Tags: cpe-onsite
James Page (james-page)
Changed in vault-charm:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Chris Sanders (chris.sanders) wrote :

Subscribing field high based on recent deployments which this the CSR processes is making miss deliveries.

Revision history for this message
Billy Olsen (billy-olsen) wrote :

As a feature request, this is not eligible for Field SLA. I have recorded this RFE on the product feedback list for prioritization.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.