Mike,

That is correct. Here is what I have discovered. I have two child portals each portal is using AD Authentication. Each portal is set to auto assign the Register and Subscriber Role. So if User A signs into Portal 1 it properly assigns them the Register and Subsciber Role. However when User A signs into Portal 2 is logs them in using the AD Authentication but does not assign them the Register and Suscriber Roles for that portal. Basically which ever portal the User signs into first is where the proper roles are assigned. Hope this helps. Let me know if you are able to duplicate the issue.

Thanks for the help.

Brian

Mike,

We are getting the following behavior when using the AD Authentication provider on multiple child portals.

We have AD Authentication enabled on one child portal but not on another child portal. When we access the portal with AD authentication the first time, we are automatically logged in with our AD credentials. If we then go to the child portal that doesn't use AD authentication and then go back to the child WITH AD authentication, our authentication is lost and we get the WindowsSignIn.aspx page.

Is this normal behavior and if so, is there a way around it?

Thanks,
Joey Navarro
Harvard-Westlake School

I did some more testing and found the following.

Assuming your site is named www.domain.com, DNN saves your cookie information on your file system as username@www.domain[1].txt. If your child portal using AD authentication is accessed via www.domain.com/child1 and your non-AD portal is www.domain.com/child2, they will share the same cookie file. So when you switch from the AD portal to the non-AD one, your AD cookie gets overwritten by the non-AD portal. One solution we found around this is to create a new portal alias for the AD portal as in child1.domain.com. This way, each portal will be using separate cookie files.

-Joey