I'm building a web application that needs to be able to scale.

We want to store a connection string, an object that says what organization the user is working on right now and the identity of the user.

We could serialize down this and send through the userdata property in the FormsAuthenticationTicket, but that feels to not be the optimal solution, because it is 4-5 strings of data that are unncessesary, but the main issue is that we are sending an encrypted connectionstring to the user which we don't want to.

So what are our options?

Can ASP.NET cache be our solution? Can we couple the expiration of the ASP.NET cache and the formsauthenticationcookie?

没有正确的解决方案

许可以下: CC-BY-SA归因
不隶属于 StackOverflow
scroll top