Repository navigation
docs(fleet-manager): add operators and make a credential request in the web UI - #74
Merged
Merged
Conversation
…he web UI Two task pages for the web UI's credential flows: an admin requesting, completing, recording and denying operator certificates, and the anonymous page where a future operator makes their own key, key backup and CSR and later builds their PKCS#12. The web UI page's Operators section and login section link to them. Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>
Contributor
Author
|
Merging for the v0.1.0 test run: CI green and mergeable at merge time. |
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Companion to the web change that brings the Operators page onto the external operator CA model (CryptOS-PKI/cryptos-web#145). Merge the two together.
Refs CryptOS-PKI/cryptos-web#144
/request-credentialpage where a future operator makes their own key, key backup and CSR, and later builds their PKCS#12, all in the browser, plus the equivalentopenssl pkcs12 -exportcommand.Callouts:
:::dangerfor the passphrase shown once (twice, one per page),:::warningfor the non-critical level extension and for denying not revoking at the CA,:::cautionbefore-you-start on each page.Merge order: with CryptOS-PKI/cryptos-web#145. It doesn't touch the lines #73 changes in
web-ui.mdandsidebars.ts, so either can merge first. Once both are in, docs#73's note that the web screens for requests aren't in this release can go.Verification
How this was verified
npm run buildcompletes with no broken links, andtask licensepasses. The screen text, button names, file names and messages were checked against the web change. The key backup and the PKCS#12 the browser builds were opened with OpenSSL 3 (openssl pkeyandopenssl pkcs12 -info: PBES2, PBKDF2-HMAC-SHA256, AES-256-CBC, the friendly name shown), and theopenssl pkcs12 -exportcommand was run as written against a PBES2 encrypted key.