Could you please let us know what kind of authentication are you using? We haven't checked the web site yet. If you are trying to use the standard membership providers, this is not possible at the moment. We will provide support for this in the Q1 release.
Could you try removing the following attribute:
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward!
We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>
Line 71: </providers>
Line 72: </siteMap>
Line 73: <roleManager enabled="true" >
Line 74: <providers>
Line 75: <clear/>
What is exact version of Sitefinity that you use? We fixed an issue with the custom Role provider in Sitefinity 4.1. Back in 4.0 this was still an issue and was not supported. If you use an older version of Sitefinity, please upgrade.
I'm glad that you solved your issue. I suppose you upgraded to 4.2 from some older version and there were some old cookies left in your browser that caused the problem.
The cookie contains information for the logged principal. Prior to version 4.1 we couldn't support ASP.NET Role providers because of a bug that was overriding our SitefinityPrincipal with a RolePrincipal. We fixed this in 4.1 so it switches the RolePrincipal with our SitefinityPrincipal. But it seems that you were logged in before upgrading and the old RolePrincipal was serialized in the cookie, so after the upgrade you were considered logged in with the RolePrincipal, while the 4.1 was expecting to have a SitefinityPrincipal. This is why deleting the cookie resulted in its recreation as SitefinityPrincipal and now everything works.