History

claire bontempo a22bb9bfcc UI: refactor to use pki/action model for importing a pem bundle (#19425 ) * rename component test file * rename component * rename file again.. * rename component file and remove import from issuer adapter * rename hbs file * update to new component name, use pki/action * update test selectors * update tests * update workflow test * add useIssuer to adapter options		2023-03-02 15:38:39 -08:00
..
addon	UI: refactor to use pki/action model for importing a pem bundle (#19425 )	2023-03-02 15:38:39 -08:00
app/utils	UI: PKI URLs section on generate-root form (#18781 )	2023-01-23 13:36:34 -06:00
config	Eslint prefer-const (#17864 )	2022-11-09 15:15:31 -08:00
index.js
package.json	UI: PKI Read Role Details (#17985 )	2022-11-21 20:09:04 +00:00
README.md	UI: PKI Generate Root Form (#18712 )	2023-01-18 12:20:44 -06:00

README.md

Vault PKI

Welcome to the Vault PKI (Ember) Engine! Below is an overview of PKI and resources for how to get started working within this engine.

About PKI

Public Key Infrastructure (PKI) is a system of processes, technologies, and policies that allows you to encrypt and sign data. (source: digicert.com)

The Vault PKI Secrets Engine allows security engineers to create a chain of PKI certificates much easier than they would with traditional workflows.

About the UI engine

If you couldn't tell from the documentation above, PKI is complex. As such, the data doesn't map cleanly to a CRUD model and so the first thing you might notice is that the models and adapters for PKI (which live in the main app, not the engine) have some custom logic that differentiate it from most other secret engines. Below are the model

pki/key

TBD

pki/role

TBD

pki/issuer

TBD

pki/certificate/*

TBD

pki/action

TBD