Feb 06, 2007 11:07 AM|wsmonroe|LINK
I have run into this bug, as it appears many others have. I'm worried though, because it seems based on the other thread about this problem that everyone is able to get around the problem by using the first workaround (disabling cookie caching in the role
manager), but in my application, that doesn't work. This troubles me. I am able to use the 3rd workaround (disable event validation on the page), so for the time being I'm OK, but I don't understand why the fix that works for everyone else doesn't work in
My situation is outlined below ... any idea why the disabling cookie caching for roles workaround won't work in this case?
I am using roles, and the page that I am having problems with manipulates users and their roles, but I am NOT using a custom provider for roles. I am using the builtin ASP.NET Sql Role provider, and a connection to my SQL db to store roles data.
My web.config, as it pertains to roles looks like:
<roleManager enabled="true" cacheRolesInCookie="false" createPersistentCookie="false">
<remove name="AspNetSqlRoleProvider" />
<add name="AspNetSqlRoleProvider" connectionStringName="LocalSqlServer" type="System.Web.Security.SqlRoleProvider, System.Web, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>