HRD and SignOut about identityserver2 HOT 4 CLOSED

OK. I played around with it in the Identity server v1 environment.

With upstream IdP
When wsignout1.0 arrives a redirect to the upstream IP is required. In theory only one per DOM session.
But the [optional] wreply parameter of the incoming wsignout1.0 must be copied. That way the upstream
IP can go to it in the end.

IdSrv is the IP
IdSrv response is a page that intitates a GET from the browser to all downstream RPs
(get "RP-enpoint-url?wa=wsignoutcleunup1.0" )
The response to wsignoutcleanup can be img or html. ADFS v2 uses:
<iframe class="NotShown" src="RP-enpoint-url?wa=wsignoutcleunup1.0"></iframe>
.NotShown { visibility: hidden; height: 1px; width: 1px; }
If there is a wreply=destination-url, then, with some javascript, the IdSrv response page should also redirect to the url in wreply. Typically OnLoad.

When wsignoutcleanup arrives, typically from above, but sometimes from below to clear partial state.
Same as being the top, but not the wreply thing.....

from identityserver2.

Hmm, my iframe was lost....

ADFSv2 uses per RP an iframe element with class="NotShown" src="RP-EndPoint-url?wa=wsignoutcleanup1.0"

from identityserver2.

Hello,

I have set up Federation between two instances of IdS and use HRD too. I have issues with Federated Sign Out, in both Hrd and WsFederation controllers the SignOutCleanupRequestMessage message types are not handled. The image source in the Federated Sign Out page is the following : https://localhost/FirstIdentityServer/issue/wsfed?wa=wsignoutcleanup1.0 (or https://localhost/FirstIdentityServer/issue/hrd?wa=wsignoutcleanup1.0).

Is this a bug or I have messed up some configurations?

from identityserver2.

SignOut is not fully done yet. It's on my todo.

from identityserver2.