f4eed5cb31
* make cross-sign component * remove type from obj-list-input * finish skeleton of component * handle change on init * finish cross-sign form * add cancel transition * update pki/issuer adapter to accept backend passed from adapterOptions * first draft of cross-signing issuers component * refactor to accommodate listing signed certs * changes to config adapter and model, likely will need to revert and manually add to pki/action * add args to infotooltip, move header to cross-sign route * use pki/action model * move header to route file * finish displaying signed certificates * finish styling * add issuer id to cross-sign breadcrumbs * add parsed cert data to requests * add status count * add error banner back |
||
|---|---|---|
| .. | ||
| addon | ||
| app/utils | ||
| config | ||
| index.js | ||
| package.json | ||
| 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