Source the CA from /ca_chain, not from issuance #2
Reference in New Issue
Block a user
Delete Branch "benvin/ca-chain-endpoint"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Deriving
ca_certificatefrom an issue response welds CA distribution to per-node renewal, so a rotation takes ~90 days to reach the estate, andissuing_cais the intermediate alone, which strict path builders reject as aCAfile.casubcommand printing{mount}/ca_chainas PEM, unauthenticatedca_certificatefrom the issue document and its file outputfull_chainleaf firstvault.addrfor the CA path viaconfig.LoadCADeriving ca_certificate from an issue response welds CA distribution to per-node renewal, so a rotation takes ~90 days to reach the estate, and issuing_ca is the intermediate alone, which strict path builders reject as a CAfile. - add a `ca` subcommand printing {mount}/ca_chain as PEM, unauthenticated - drop ca_certificate from the issue document and its file output - order full_chain leaf first - require only vault.addr for the CA path via config.LoadCA