Repository navigation
[2/2] Add standalone SCEP gateway, Compose deployment and image workflow - #19
Merged
Merged
Conversation
This was referenced Oct 22, 2026
tilwegener
marked this pull request as ready for review
October 22, 2026 18:09
oriolrius
added a commit
that referenced
this pull request
Oct 22, 2026
kms/kms.toml used `[server]` and `[database] type/path`, which Cosmian KMS 5.24 silently ignores. The dev and e2e KMS therefore kept SQLite in the container's writable layer, the mounted ./data stayed empty, and recreating the container lost every key. Switch to the 5.24 schema (`[http]`, `[db] database_type/sqlite_path`, `[workspace]`, `[logging] rust_log`), identical to the file proposed in #19, so that PR merges cleanly. Document in kms/README.md how to rescue a database left inside an old container, ignore the SQLite WAL/SHM files, and note that RUST_LOG is ignored in config-file mode. Production (k5-stack-pki) is unaffected: it runs the KMS in default mode with the data dir mounted at /var/lib/cosmian-kms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tilwegener
force-pushed
the
feat/scep-gateway-only
branch
from
October 22, 2026 21:30
77709c8 to
93e03b8
Compare
oriolrius
approved these changes
Oct 23, 2026
oriolrius
left a comment
Owner
There was a problem hiding this comment.
Approved together with #18 — see the review there for details. Thanks @tilwegener!
oriolrius
force-pushed
the
feat/scep-gateway-only
branch
from
October 23, 2026 13:53
d2d7487 to
ff6e34b
Compare
oriolrius
added a commit
that referenced
this pull request
Oct 24, 2026
kms/kms.toml used `[server]` and `[database] type/path`, which Cosmian KMS 5.24 silently ignores. The dev and e2e KMS therefore kept SQLite in the container's writable layer, the mounted ./data stayed empty, and recreating the container lost every key. Switch to the 5.24 schema (`[http]`, `[db] database_type/sqlite_path`, `[workspace]`, `[logging] rust_log`), identical to the file proposed in #19, so that PR merges cleanly. Document in kms/README.md how to rescue a database left inside an old container, ignore the SQLite WAL/SHM files, and note that RUST_LOG is ignored in config-file mode. Production (k5-stack-pki) is unaffected: it runs the KMS in default mode with the data dir mounted at /var/lib/cosmian-kms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
oriolrius
pushed a commit
that referenced
this pull request
Oct 24, 2026
…orkflow (#19) RSA SCEP gateway (shared/Intune/webhook authorization) that reaches the KMS only through the backend RA API, with short RA snapshots, tolerant startup renewal, HTTPS-only backend URL, Compose templates and protocol/deployment docs. Same-key RA renewal requires Cosmian KMS 5.28.0; dev/deployment/e2e KMS pins move to 5.28.0.
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.
Add the optional RSA SCEP gateway, shared/Intune/webhook authorization, Compose templates, protocol documentation and image workflow. Existing installations reuse the backend and add one gateway container.
Depends on #18. This branch is now stacked on the updated #18, rebased on current upstream main (213167c, including #20). Its branch history therefore includes the foundation until #18 is merged. Deployment/KMS Compose conflicts are resolved, retaining both runbook blocks.
Review 5620708940 — #19 corrections
ansible/tests/e2e/docker-compose.ymlare aligned at 5.28.0, and thekms.tomlheader is updated.Backend-owned RA boundary
No gateway KMS client, KMS credentials, private keys or KMS object IDs. Provision/renew/sign/decrypt go through backend integration-scoped RA endpoints from #18. Compose separates the backend's internal KMS network from the gateway. Shared DN policy, stable renewal subject/SANs, bounded body reads, per-CSR coordination, transient Intune journal retention and protected RA serials are included.
KMS 5.28.0 supplies fresh serials on same-key RA renewal; 5.24 cannot safely provide this. The upgrade runbook requires backup, staging on a copy and retention of old images/data. The direct-KMS gateway migration requires CA rediscovery for the new backend-bound RA. No production data was migrated.
Use one gateway replica while cross-replica device issuance uniqueness is pending. Live Intune/physical-device acceptance and optional image signing/SBOM/scanning remain deployment/follow-up work. MDM/client profiles schedule client renewal separately from automatic RA renewal.