This project has moved and is read-only. For the latest updates, please go here.

Ws-Federation Middleware Handling wsignout1.0 and/or wsignoutcleanup1.0

Jun 12, 2014 at 5:21 AM

From what I can see from the source, the current beta middleware doesn't support this yet?

I'm wanting to call a signout to my relying parties after a user signs out of the identity provider.

When is this expected to be implemented? or have I missed something?
Jun 12, 2014 at 1:22 PM
It can send sign-out messages to the identity provider, but it cannot currently receive them. This feature is planned for vNext.
Jun 26, 2014 at 8:19 PM
What does vNext mean? Post Katana v3?
Jun 26, 2014 at 8:22 PM
Yes, post v3.
Jun 26, 2014 at 9:34 PM
DominickBaier wrote:
What does vNext mean? Post Katana v3?
See to get more info about vNext.
Sep 17, 2014 at 11:27 AM
It is a lot of information at vnext. Where is it located? Can I get it from nuget?
Sep 17, 2014 at 5:34 PM
See for getting vNext.
Jun 29, 2015 at 7:01 PM
Edited Jun 29, 2015 at 7:02 PM

I was wondering, is there a suggested workaround before vNext? What should we do with the cleanup messages? I tried handling it, but if I call Signout() explicitly, I get the redirects...
Jul 14, 2015 at 7:41 PM
Sorry for the delay, I tried forwarding this to someone more familiar with WSFed but didn't get anything. It sounds like you have already intercepted the cleanup message. The only thing left to do is to delete the application cookie. You could do this via SignOut("Cookie") or directly via HttpResponse.Cookies.Delete.