Skip to content

Require signed auth for DWS security routes#29

Open
lawyered0 wants to merge 2 commits intoJejuNetwork:mainfrom
lawyered0:codex/dws-security-auth
Open

Require signed auth for DWS security routes#29
lawyered0 wants to merge 2 commits intoJejuNetwork:mainfrom
lawyered0:codex/dws-security-auth

Conversation

@lawyered0
Copy link

Summary\n- require signed wallet auth headers for /security routes outside localnet\n- keep public WAF reads, but protect all mutation and sensitive read endpoints\n\n## Testing\n- not run (not requested)

@lawyered0
Copy link
Author

Why this change: /security routes trusted x-wallet-address alone. That allows any caller to spoof admin actions (WAF rules, API keys, secrets, audit reads). This enforces signed x-jeju-* headers in non-localnet while keeping public WAF reads unchanged.

@lawyered0
Copy link
Author

Follow-up: accept legacy x-wallet-address as the address source for signature validation (still requires x-jeju-timestamp/signature), so existing clients can transition without breaking.

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