What would be the best way to handle SSO on a small group of DNN sites? Keep each one a separate instance or create a main site,  then create subportals off of it? Ideally, I would like to keep them separate (as different business units) so that it would facilitate the sale of one of those units in the future. From what I've read it's impossible to separate subportals from the main. Also, if I chose the separate instance route, what recommendations would you have for an SSO solutions (i.e. vendor)?

Thanks,

Will

I guess my first question should have been, does DNN have any SSO capabilities built in to the system? For instance, can a member of  a master portal be given rights or access for membership in a sub portal? Second, are there any viable solutions for SSO between distinct DNN sites that you know of? There a couple of SSO modules on Snowcovered, but they don't appear to be reliable based on customer comments.



As for authentication, the main one we use or offer members if SSL and Windows Live I.D. Oauth may be next.































 































Will 

Thanks, Leopold. I had visited their site before and I just wrote them asking if they had any other tools that could accomodate us. They said that they only support subportal SSO and vice versa, not separate instances of DNN. I suppose the only option is to consolidate the sites or go the federated auth route. Problem is, third party auth aren't so federated. No single auth scheme has become the de facto standard.