有关与WIF一起使用的cookie的问题 [英] Questions about the cookies used with WIF

问题描述

我正在使用针对SAML 2.0的WIF扩展，并且最近遇到了与SSO过程中生成的cookie相关的问题。 当用户验证应用程序时，它会生成几个cookie，例如：

I'm using the WIF Extension for SAML 2.0 and recently ran into an issue related to the cookies generated during the SSO process.  When a user authenticates the application it generates several cookies, for example:

• FedId
• FedAuth
• FedAuth1
• [第四个cookie名称是GUID，每个SSO都有变化]

那个使用GUID的最后一个cookie在一段时间内变得非常大 时间，我不知道为什么会这样，如果有什么我可以做的，以管理它的大小。 如果我解码那个cookie值，它似乎是从0开始的计数器，对于
例如：

That last cookie with the GUID has grown extremely large over a period  of time and I'm not sure why it is, and what if anything I am able to do to manage it's size.  If I decode that cookie value it just seems to be counter starting at 0, for example:

0; 1; 2 ; 3; 4; 5; 6; 7; 8; 9; 10; 11; 12; 13; 14; 15; ....
3110; 3111; 3112; 3113; 3114; 3115; 3116; 3117; 3118; 3119; 3120; 3121; 3122; 3123

目前看来GUID cookie被破坏了以每件大约4k的价格进入20个以上的块。 这会为客户端生成400个错误，因为标头大小太大，IIS无法处理。 有没有其他人遇到过这个问题，
或者知道一种方法来限制这个cookie的大小，以便它不会达到这么大的尺寸？

Currently it appears that the GUID cookie gets broken up into upwards of 20 chunks at approximately 4k a piece.  This is generating 400 errors for the clients as the header size is too large for IIS to handle.  Has anyone else run into this issue, or know of a way to limit the size of this cookie so that it doesn't reach a size so large?

推荐答案

我的组织正在遇到同样的问题。 你找到了决议吗？

My organization is experiencing this same issue.  Have you found a resolution yet?

这篇关于有关与WIF一起使用的cookie的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！