asp.net - How to track expired WIF fedauth cookies? -


i have interesting problem trying keep track of expired wif authentication sessions/cookies.

as bit of background: site mvc 3, uses windows identity foundation (wif) has trust adfs server sts. entire site protected ssl. sts has token expiry set 60 minutes.

when user signs out manually, call signout method on fedauth module:

federatedauthentication.wsfederationauthenticationmodule.signout(false); 

this of course removes fedauth cookies, here's problem starts. if capture cookies fiddler, can re-present them site within expiry time , still treated logged in.

i realise being performed privileged position of browser having accepted fiddler proxy... customer worried auth cookies not being expired presents significant security risk. they're not convinced ssl protects site sufficiently, , if attacker execute mitm attack, use cookies after user thinks have logged out.

i have explained if vulnerable after log out, vulnerable during log in, don't care...

so have looked ways sure once user logs off, fedauth cookies associated logon session treated expired. wif handlers don't seem have built in mechanism tracking expired tokens, , have not found else related this.

i guess in fact wider problem -> how detect expired cookies in general? valid cookie valid cookie!

the obvious solution track cookies after logout somehow, i'd avoid custom code route if possible; noob, lot of security literature says avoid custom coding kind of session mechanics, wrong!

is aware of standard solutions in asp.net problem?

thanks in advance.

you don't without keeping server-side list of tokens revoked. why rely upon inherent expiration https prevent token being leaked/stolen.


Comments

Popular posts from this blog

apache - Remove .php and add trailing slash in url using htaccess not loading css -

javascript - jQuery show full size image on click -