Repository navigation
feat: vault cert-proof sessions and deploy CLI gRPC cert init - #147
Merged
Merged
Conversation
getVaultSessionToken unwraps the system member key, signs a server nonce, and calls CreateSessionByCert. Serial-only CreateSessionManaged is no longer used. Missing durable member keys fail closed with MEMBER_KEY_UNAVAILABLE.
Enable control-plane TLS with a dedicated gRPC CA. Compose and Swarm mount server and API client certs; the API presents the client cert. Vault sessions already use cert proof; serial-only mint is gone on the miniKMS side.
…S gRPC certs sha-60e2feb dropped ManagedAuth, so CreateSession now requires cert_auth. Mint sessions via IssueSessionChallenge + member-key signature, enable control-plane mTLS, and have the deploy CLI write missing gRPC PEMs on init/upgrade.
7 of 9 tasks
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.
Why
Tag
v0.23.0(b3164e4f) pinned miniKMSsha-60e2feb, which dropped serial-onlyManagedAuth. Release E2E (run 36268240078) failed 86 tests with:INVALID_ARGUMENT: cert_auth is requiredThe tag-release Action was cancelled. This recut folds PR #145 into 0.23.0 so the API, compose, and deploy CLI match the pinned sidecar.
What
IssueSessionChallenge+ ECDSA-signed nonce viaCreateSessioncert_authwriteMinikmsGrpcTlsIfMissing()generates P-256 control-plane CA/server/client PEMs under/opt/envsync/deploy/on init/upgrade when any file is missingpackages/envsync-apican load themMINIKMS_TLS_ENABLED=falseover.env.e2e.testAfter merge
v0.23.0v0.23.0on the newmainHEAD