I'm evaluating Dynamic Login right now, and I've run into what might be a serious gap in my understanding.

In my experience, you should achieve your desired result if:

• You properly configure SSO through the Control Panel;
• Your users login with the 'remember me on this computer' field checked on; and
• Your portals are handled through child portals, as opposed to sub-domains.

At least we were a ble to achieve your results through the above configuration.

Hope this helps.

Thanks for the quick reply, Mark. 

Hi Peter,

Thank you for your questions... I understand what you are looking for and in general I REALLY wished that our module could handle this requirement but at this time its not possible.

Basically "Single Sign On" can mean a couple different things, in this case and for our module Single Sign On means that:
1. The user can use the same username and password as the other site
AND
2. Authentication will persist if the domain never changes, so the user can move between portals without having to sign in, but only if the user is moving from theirdomain.com/child and not child.theirdomain.com.

Basically, the sign on portion is coming from Dynamic Login but then after Dynamic Login what is really happening is not actually logging in but how ASP.NET and DotNetNuke Authentication itself works. Authentication is setup based on a cookie variable and is unique for the domain. So for example, if you signed into your site at www.yoursite.com and then you navigated to just yoursite.com or somethingelse.yoursite.com the authentication itself will not persist (even as a host user).

We have reviewed adding this into Dynamic Login but had to hold of because it was working in FireFox but no in IE when we implemented similar code and steps as described here:
http://davestechshop.net/FormsAuthC...mainNames2

So, this is something we are still researching, there are actually a few steps I have read about that you might try and report back to us your findings... These include:

1. Modifying your web.config as described here:
http://stackoverflow.com/questions/...ub-domains

Basically I believe in the authentication section of your web.config you need to include domain=".domain.com". This should then let everything work that is before the .domain.com. I believe I found this was working on FireFox but not IE though.


Thanks!

-Chad

Thanks very much, Chad, for your clear, complete, and helpful answer.

I'm off to investigate these issues. I seriously appreciate you highlighting the technical points for me.

Thanks again. I'm hoping my reseach will be fruitfull and that I'll be able to use Dynamic Login and Dynamic Registration.

Peter

It seems things are not QUITE so simple.

The good news: YES, changing the web.config does indeed work. It works in all browsers that I've tested. It's actually documented to work by Microsoft. Well, partially documented. Sort of. Kind of.

The bad news: It SEEMS that there's a bit of a problem with this approach when you sign-in on PortalA.xyz.com and then surf on over to PortalB.xyz.com -- IF the DNN username (and/or security roles) you signed-in with exist on PortalA but not on PortalB. Strange things sometimes happen. And what DOES happen appears to depend on the browser you're using. I'm starting to lose my appreciation for Chrome, for example.

ANYhow, I'm going to leave this here for now, and see if Mr. Nash or any of the other DataSprings folks have any further comments.

I'm going off to scratch my head a bit and think of what I should do next.

Peter