Are you using a v4.7 version of umbraco... cause that version has some issues when logging out using asp.net membership, it still keeps you logged in, even if you're next logging in as someone else...
Thanks , I was able to resolve the issues with the login "caching" found out it was the ASP.net session cookie staying persistant in the browser session. So I now have to just use the fix's for connecting the asp.net membership and facebook connect authentication together, or figure out the best migration strategy.
Mixing facebook connect and ASP.net Membership
I am having an issue where when I associate my facebook account using the facebookconnect package 1.1 (by René Pjengaard), and the asp.net membership controls; When Im logged out of the ASP.net membership, the REMOTE_USER still shows associated..
Any idea where this is stored? I checked all the membership tables in the SQL DB, I couldnt locate it.
Show the login prompt, but doing a ?umbdebugshowtrace=true shows that im logged in as a user I created (and subsequently deleted for testing purposes)
Are you using a v4.7 version of umbraco... cause that version has some issues when logging out using asp.net membership, it still keeps you logged in, even if you're next logging in as someone else...
As long as v4.7.1 is not out, you'll have to revert to a "fix", which can be found in nForum's project code on Codeplex.
Hope this helps.
Regards,
/Dirk
Thanks , I was able to resolve the issues with the login "caching" found out it was the ASP.net session cookie staying persistant in the browser session. So I now have to just use the fix's for connecting the asp.net membership and facebook connect authentication together, or figure out the best migration strategy.
is working on a reply...