Question

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?

No correct solution

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top