Some time ago Charles Nurse published a DotNetNuke Roadmap^* describing a framework for allowing a user to register with >1 portals within a single site and retain their identity (UserInfo) within each protal that they register with. The specific feature was called Single Sign-On/Portal Groups. I'm wondering what, if anything, has been done in terms of implementation of this feature.

For our purposes we need a feature like this, in order to allow users to navigate between portals using a single set of authentication credentials (single sign-on), without requiring complex mediation by our application (eg automating DNN authentication by logging in to each portal on user's behalf when navigating between portals).

The main issue for us, if we have to mediate using the existing DNN user/portal mappings, is that it looks like we need to create a distinct user account on each portal and then we have to hook into user account/profile changes on each portal and propagate them to other portals that the user registers with. I'm not comfortable with this approach as It would be complex and would easily break if any changes to user registration were implelmented in future DNN releases.

Is there anything on the DNN roadmap to address this (single sign-on to >1 portals)? If so, is the proposed solution documented for review and what is the anticipated timeframe for produciton release?

Also: Along with this problem there is the question of how to manage user profile settings. Some profile settings (eg, phone number) are user-bound properties that should be the same regardless of which portals the user registers with. But the DNN data model (it seems to me) binds profile information to user-portal (see Profile table in DNN 4.5.4 data model). Role management would also interact with the single sign-on/multiple portals feature. Has there been any discussion of how to manage profile property and role assignment in relation to this feature?