Space keys on split deployments (remoteUrl): move migration and key admin to the crypto role #1019

Open
opened 2026-10-26 22:55:35 +00:00 by Cordy · 0 comments
Owner

Follow-up from #1002 stage 3 (controller decision D-S10, v0.6.358).

On a split deployment, the API pods hold no custody credentials. The key custody runs in a separate crypto role (remoteUrl). In v0.6.358 the API role there keeps the v0.6.357 lookup by name:

  • no key reference is written;
  • the key admin routes answer 409 key-custody-remote;
  • the Encryption page shows blocked: key-custody-remote.

So #965's fix (a reused name never inherits a key) does not apply to split deployments yet. No instance runs split today.

To decide and build: the crypto role runs the move and the key admin (rotate, check, remove old copies, destroy), and the API role forwards those admin calls. Giving the API role custody credentials would defeat the split. Research first, per the playbook.

Follow-up from #1002 stage 3 (controller decision D-S10, v0.6.358). On a split deployment, the API pods hold no custody credentials. The key custody runs in a separate crypto role (`remoteUrl`). In v0.6.358 the API role there keeps the v0.6.357 lookup by name: - no key reference is written; - the key admin routes answer 409 `key-custody-remote`; - the Encryption page shows `blocked: key-custody-remote`. So #965's fix (a reused name never inherits a key) does not apply to split deployments yet. No instance runs split today. **To decide and build:** the crypto role runs the move and the key admin (rotate, check, remove old copies, destroy), and the API role forwards those admin calls. Giving the API role custody credentials would defeat the split. Research first, per the playbook.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#1019
No description provided.