-
Notifications
You must be signed in to change notification settings - Fork 0
Security
4nass edited this page Aug 19, 2026
·
1 revision
Read the main repository's security policy before reporting a vulnerability.
-
IDMUX_SESSIONnever contains a clear IdP session ID. - AES-256-GCM encrypts and authenticates the complete client state.
- Every encryption uses a fresh random nonce.
- The encryption key is never logged or returned in a response.
- Session cookies are
HttpOnly,Secure, andSameSite=LaxorStrict. -
IDMUX_SESSIONis never forwarded to the IdP. - An upstream request contains zero or one IdP identity cookie.
-
authuser=newsends no IdP identity cookie upstream. - Logout removes only the selected session slot.
- Invalid input returns a safe response and never causes a panic.
- Logs never contain cookie values, keys, tokens, or IdP session IDs.
Use IDMUX_ENCRYPTION_KEY for the new key and
IDMUX_ENCRYPTION_KEY_PREVIOUS for old keys during a planned rotation.
Remove old keys only after old cookies have expired.
Never add real cookies, tokens, keys, customer data, or production logs to a wiki page, issue, pull request, or commit.