本文介绍了在WIF中使用带有SAM和Thinktecture IdentityModel的滑动会话时,使用新的SessionSecurityToken更新BootStrapContext的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

如。
发出并写入cookie的会话安全令牌已根据需要扩展为有效期,并相应地设置了cookie。

When using sliding sessions in WIF with the session authentication module (SAM) and Thinktecture IdentityModel as described in brockallen's blog.The session security token issued and written to the cookie has it's "valid to" extended as required and the cookie is set accordingly.

但是,BootStrapToken已序列化根据目前的说法,身份仍然是旧的,并且令牌可能已过期。当出于各种原因尝试使用引导上下文令牌时,这会导致问题(其中可能是)。

But, the BootStrapToken serialized to the current claims Identity remains the old one, with the potentially expired token. This causes problems when trying to use the bootstrap context token for different reasons (among them could be Implementing "Poor Man"’s Delegation) .

用新发行的令牌更新引导令牌的最佳方法是什么?

What is the best way to update the bootstrap token with the new issued token?

推荐答案

获取新的引导程序令牌的唯一方法是与实际发行者进行往返。

The only way to get a fresh "bootstrap" token is to do a roundtrip to the actual issuer.

这篇关于在WIF中使用带有SAM和Thinktecture IdentityModel的滑动会话时,使用新的SessionSecurityToken更新BootStrapContext的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-21 08:34