OWIN cookie认证的中间件并不支持类似功能会话缓存呢。 ＃2不是选项。

＃3是正确的道路要走。作为Prabu建议，你应该做在你的code以下内容：

OnResponseSignIn：

• 保存context.Identity与唯一的密钥（GUID）高速缓存


• 创建嵌入了独特的键的新ClaimsIdentity


• 新身份置换context.Identity

OnValidateIdentity：

• 从context.Identity获取唯一键索赔


• 以独特的键获取缓存的身份


• 与缓存的身份拨打context.ReplaceIdentity

我要建议你gzip压缩的饼干，但我发现OWIN已经做了，在其TicketSerializer。不是你的选择。

I have an application that used to use FormsAuthentication, and a while ago I switched it to use the IdentityModel from WindowsIdentityFramework so that I could benefit from claims based authentication, but it was rather ugly to use and implement. So now I'm looking at OwinAuthentication.

I'm looking at OwinAuthentication and the Asp.Net Identity framework. But the Asp.Net Identity framework's only implementation at the moment uses EntityModel and I'm using nHibernate. So for now I'm looking to try bypassing Asp.Net Identity and just use the Owin Authentication directly. I was finally able to get a working login using the tips from "How do I ignore the Identity Framework magic and just use the OWIN auth middleware to get the claims I seek?", but now my cookie holding the claims is rather large. When I used the IdentityModel I was able to use a server side caching mechanism that cached the claims on the server and the cookie just held a simple token for the cached information. Is there a similar feature in OwinAuthentication, or would I have to implement it myself?

I expect I'm going to be in one of these boats...

1. The cookie stays as 3KB, oh well it's a little large.
2. Enable a feature similar to IdentityModel's SessionCaching in Owin that I don't know about.
3. Write my own implementation to cache the information causing the cookie to bloat and see if I can hook it up when I configure Owin at application startup.

4. I'm doing this all wrong and there's an approach I've not thought of or I'm misusing something in Owin.

   public class OwinConfiguration
   {
       public void Configuration(IAppBuilder app)
       {
           app.UseCookieAuthentication(new CookieAuthenticationOptions
           {
               AuthenticationType = "Application",
               AuthenticationMode = AuthenticationMode.Active,
               CookieHttpOnly = true,
               CookieName = "Application",
               ExpireTimeSpan = TimeSpan.FromMinutes(30),
               LoginPath = "/Login",
               LogoutPath = "/Logout",
               ReturnUrlParameter="ReturnUrl",
               SlidingExpiration = true,
               Provider = new CookieAuthenticationProvider()
               {
                   OnValidateIdentity = async context =>
                   {
                       //handle custom caching here??
                   }
               }
               //CookieName = CookieAuthenticationDefaults.CookiePrefix + ExternalAuthentication.ExternalCookieName,
               //ExpireTimeSpan = TimeSpan.FromMinutes(5),
           });
       }
   }
   

UPDATE I was able to get the desired effect using the information Hongye provided and I came up with the below logic...

Provider = new CookieAuthenticationProvider()
{
    OnValidateIdentity = async context =>
    {
        var userId = context.Identity.GetUserId(); //Just a simple extension method to get the ID using identity.FindFirst(x => x.Type == ClaimTypes.NameIdentifier) and account for possible NULLs
        if (userId == null) return;
        var cacheKey = "MyApplication_Claim_Roles_" + userId.ToString();
        var cachedClaims = System.Web.HttpContext.Current.Cache[cacheKey] as IEnumerable<Claim>;
        if (cachedClaims == null)
        {
            var securityService = DependencyResolver.Current.GetService<ISecurityService>(); //My own service to get the user's roles from the database
            cachedClaims = securityService.GetRoles(context.Identity.Name).Select(role => new Claim(ClaimTypes.Role, role.RoleName));
            System.Web.HttpContext.Current.Cache[cacheKey] = cachedClaims;
        }
        context.Identity.AddClaims(cachedClaims);
    }
}

OWIN cookie authentication middleware doesn't support session caching like feature yet. #2 is not an options.

#3 is the right way to go. As Prabu suggested, you should do following in your code:

OnResponseSignIn:

• Save context.Identity in cache with a unique key(GUID)
• Create a new ClaimsIdentity embedded with the unique key
• Replace context.Identity with the new identity

OnValidateIdentity:

• Get the unique key claim from context.Identity
• Get the cached identity by the unique key
• Call context.ReplaceIdentity with the cached identity

I was going to suggest you to gzip the cookie, but I found that OWIN already did that in its TicketSerializer. Not an option for you.