Skip to content

Require signed auth for DWS KMS access#34

Open
lawyered0 wants to merge 4 commits intoJejuNetwork:mainfrom
lawyered0:codex/dws-kms-auth
Open

Require signed auth for DWS KMS access#34
lawyered0 wants to merge 4 commits intoJejuNetwork:mainfrom
lawyered0:codex/dws-kms-auth

Conversation

@lawyered0
Copy link

Summary\n- require signed wallet auth for KMS key/secret operations outside localnet\n- restrict key and secret listing/details to the authenticated owner\n- enforce owner checks on signing requests\n- require auth for encrypt/decrypt endpoints\n\n## Testing\n- not run (not requested)

@lawyered0
Copy link
Author

Why this change: KMS routes allowed unauthenticated key/secret listing, key details, and signing. That makes secrets enumerable and signable by anyone. This enforces signed x-jeju-* headers for non-localnet and ensures ownership checks on key/secret access.

@lawyered0
Copy link
Author

Follow-up: close the service-id bypass by requiring a shared service token (KMS_SERVICE_TOKEN / DWS_KMS_SERVICE_TOKEN / SERVICE_AUTH_TOKEN) for x-service-id access outside localnet, and update the local inference provider to send that token.

@lawyered0
Copy link
Author

Follow-up: /kms/vault/diagnostics now requires auth and only returns total secret count for service-id callers. Regular users only see their own count.

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