.net - Sign out In ADFS2.0 with WIF application -
i have followed this link understand wif application adfs 2.0 , installed adfs2.0 , sample application (in iis) in same machine,now can login sample application active directory username , password ,but problem ,although sign out sample application redirects me login.aspx page when click button in browser , refresh can still logged in ,that means session not expiring in application .do need clear logged in session in adfs ?if how can ?i have used "federatedpassivesigninstatus" tool assumed logout both application , adfs .
this demo in gif.
<wif:federatedpassivesigninstatus id="federatedpassivesigninstatus1" runat="server" onsignedout="onfederatedpassivesigninstatussignedout" signinbuttontype="link" federatedpassivesignout="true" signoutaction="federatedpassivesignout" /> protected void onfederatedpassivesigninstatussignedout(object sender, eventargs e) { wsfederationauthenticationmodule authmodule = federatedauthentication.wsfederationauthenticationmodule; string signoutendpoint = "https://test-server.test.localhost/claimsawarewebappwithmanagedsts/login1.aspx"; // can stored in configuration app settings string signouturl = wsfederationauthenticationmodule.getfederationpassivesignouturl(signoutendpoint, authmodule.realm, null); wsfederationauthenticationmodule.federatedsignout(new uri(signouturl), new uri("https://test-server.test.localhost/claimsawarewebappwithmanagedsts/default.aspx")); }
it looks cookie cleared out browser. however, cookie created sts not. need ensure sts correctly receiving signout request should case when using federatedsignout.
there signout method link: claims aware mvc4 app using wif identity , access tool in .net 4.5 part ii
if (httpcontext.request.isauthenticated) { wsfederationauthenticationmodule instance = federatedauthentication.wsfederationauthenticationmodule; instance.signout(false); signoutrequestmessage request = new signoutrequestmessage(new uri(instance.issuer), instance.realm); return new redirectresult(request.writequerystring()); }
Comments
Post a Comment