This project has moved. For the latest updates, please go here.

wsfederation middleware, savesignintoken, bootstrap context

Apr 1, 2014 at 6:24 AM
one can configure the classical WIP pipeline to expose the security token to the app, for use in delegated WCF scenarios where the websso token is injected into the WCF client proxy.

How do I get the token in OWIN, having completed wsfederation?

I tried the obvious: set security token handlers config to savebootstrapcontext (no effect).

Similarly, tried to set tokenvalidationparameters savesignintoken (which may work, but I dont know where to go looking for the saved value...)

Looked in the obvious place for the saved token - on claimsidentity.bootstraptoken - which is where Id expect it, alongside the claims.

FYI, I processing a JWT inbound from ws-fedp handshake, if that makes any difference.
Apr 1, 2014 at 6:53 AM
http://yorkporc.wordpress.com/2014/03/31/capture-owinkatana-ws-fedp-security-token/

is my best so far - just setting an event handler for ontokenreceived.
Developer
Apr 30, 2014 at 6:08 PM
We don't save the bootstrap context in the cookie, so it would get lost when the ClaimsIdentity is serialized into the cookie.
We are planning on fixing that.

Do you see the bootstrapcontext in the ClaimsIdentity before it was serialized?
Coordinator
Apr 30, 2014 at 6:10 PM
Brent, please file a bug to fix the bootstrapcontext serialization, I don't think there's one tracking that yet.
Developer
Apr 30, 2014 at 6:15 PM
I had filed:



Sent from Windows Mail