4af59fd6cd
* add show page for generated CSR * fix typo, make key-id copyable * add tests * move pki tests to designated folder * list keys when in between state after CSR generation * uses customTTL for generateing role cert and adds privateKeyFormat * Revert "move pki tests to designated folder" This reverts commit 82b60e4beab0717bbace8dee64cc0863a5488079. * Revert "add tests" This reverts commit 3c90fc9abacf8309d2cf9f1b90299a5153b743da. * Revert "fix typo, make key-id copyable" This reverts commit 8e6f5a1f4580229e6de8f6e919945f03ee29ac3d. * revert accidental parent commits * Revert "list keys when in between state after CSR generation" This reverts commit c01d7852a46d41a72e5eace28aafed5daa93f70f. * fix empty arrays removed when serialized * fix comment; g * update test |
||
---|---|---|
.. | ||
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