Skip to content

fix(rest_api): register custom server public key with the KSM SDK - #2447

Merged
maksimu merged 1 commit into
smk-testfrom
fix/smk-ksm-sdk-server-key
Oct 16, 2026
Merged

maksimu merged 1 commit into
smk-testfrom
fix/smk-ksm-sdk-server-key

Conversation

@maksimu

@maksimu maksimu commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator

KEEPER_SERVER_PUBLIC_KEY was only loaded into Commander's own key table. The embedded KSM SDK keeps a separate one, so slack-app-setup, service-mode docker setup and ksm app client add failed against SMK at the first sm/v1/get_secret. The server asked for key_id 7 (401), the SDK encrypted with Keeper's hard-coded key 7, and SMK returned 400 encrypted transmission key is invalid.

This change writes the same key into keeper_secrets_manager_core.keeper_globals.keeper_public_keys, which core.py reads directly. I checked locally that with the env vars set the SDK's key 7 becomes the SMK key and transmission keys are built with it, and that without them the table is unchanged. I haven't yet re-run slack-app-setup end to end against SMK.

@maksimu
maksimu marked this pull request as ready for review October 16, 2026 15:24
@maksimu
maksimu merged commit c036b9a into smk-test Oct 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant