You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to harden mod_auth_openidc-protected location against cookie stealing attacks. The most simple (yet effective) defense seems to be binding session to user IP address and invalidating it if user IP address has changed.
I'm wondering if it's possible to achieve this somehow using only mod_auth_openidc and Apache. I've considered inserting client IP address in some claim and using Require claim/Require claim_expr to match it against %{REMOTE_ADDR} (triggering step-up auth logic on mismatch), but this gets complicated if you're already using them for other requirements (also, this fails if client IP address seen by OP server is different from address seen by RP server - for example, if OP server is SaaS/externally hosted).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to harden mod_auth_openidc-protected location against cookie stealing attacks. The most simple (yet effective) defense seems to be binding session to user IP address and invalidating it if user IP address has changed.
I'm wondering if it's possible to achieve this somehow using only mod_auth_openidc and Apache. I've considered inserting client IP address in some claim and using
Require claim
/Require claim_expr
to match it against%{REMOTE_ADDR}
(triggering step-up auth logic on mismatch), but this gets complicated if you're already using them for other requirements (also, this fails if client IP address seen by OP server is different from address seen by RP server - for example, if OP server is SaaS/externally hosted).Beta Was this translation helpful? Give feedback.
All reactions