Thanks for the info Dan. I see the Gemini case was closed as could not reproduce. I'll do some testing this weekend and see if I can't reproduce it.

I just found some time to test this a little against a DotNetNuke 6.1.3 install and so far I can recreate the problem you're seeing. If I automatically login I lose SuperUser permissions but if I manually login I retain SuperUser permissions. I don't even have to wait for the AppPool to recycle just log out and hit windowssignin.aspx.

Can you test this scenario as well and see if you get the same result? In the meantime I'll try to investigate to see if i can figure out what's different in the user objects that I'm pulling from the database.

How I tested was log out of the site, set my user as SuperUser in the database, and browse to windowssignin.aspx. Then check the database again and see that my account was no longer a SuperUser. Then set my account as SuperUser again and then manually login.

On automatic login I lost Host access but on manual logins I retained it. I'm pretty sure that I've got it fixed and checked into CodePlex (http://dnnauthad.codeplex.com/workitem/7424). I'm not sure what changed in the core code but it's something I should've been checking anyway.

I'm hoping to get a couple more bugs fixed this week and then release a release candidate of the provider for more widespread testing.