One issue that is confronting you now and again as a dotnetnuke expert is the smoldering yearning of clients to have a solitary sign-on answer for their multi-entryway framework. Regularly they have diverse entryways for their organization offices or separate intranet and web entrances or some other multiportal needs. At the same time none of these clients comprehend the need of logging seperatly into each and every entryway! What's more for the framework executives it is a bad dream to keep all these client accounts in sync! A considerable measure of business and open source modules and suppliers served to take care of this issue previously.

An alternate inconvenience is the inconceivability to impart content between entries. Consider  a desktop program site and his portable friendly (acknowledged as two entries). On the off chance that you compose an article in the desktop gateway and you need to demonstrate this uncommon article on the portable entry as well, what did you need to do ? Yes, duplicate and glue! Conceivable, however not exceptionally rich!

Since Version 6.1  of Dotnetnuke  there is an answer for this in the Proffessional Version (PE). Lamentably this should be excluded in the group version of DNN. Yet you ought to realize that the usefulness is actualized in the center and just the organization module is inadequate in the CE form! So you have the capacity utilize this, even in  CE, with negligible changes straightforwardly in the database:

Base of all the functionality is the new table “PortalGroups”:

For every group of portals we need to insert here one record:

Next to the Portalgroupname and the Portalgroupdescription, which are selfexplaining, and the normal fields Createdondate, Createdbyuserid and so forth , just  Masterportalid and Authenticationdomain  are intriguing. Masterportalid  ought to be supplanted with the portalid of the entryway which ought to be utilized as the entry where the client logs later on. Authenticationdomain ought to be loaded with the space name of the expert entryway (e.g. www.yourdomain.com)

Presently we need to fill in the Portalgroupid of the recently made portalgroup into the field with the same name in the comparing Portal records and our SSO arrangement is finished:

Tip: Eventually you have to recycle the Applicationpool to see your results!

And now see how this affects your portal administration:

Add an existing module – before

Add an existing module – after

And after login in the main portal the user is also automatically logged in into the child portal and all users of both portals show up together in the user administration!

Please make a special effort to be mindful of this:

• A client made on the expert entryway is known on all entrances of the entrance bunch
• Login at an entryway consequently logs you into all entrances with the same area (incl. subdomains + childportals). SSO for different areas does NOT work (yet you can log in with the same client certifications)

Best DotNetNuke Hosting Recommendation

ASPHostPortal.com
ASPHostPortal.com provides its customers with Plesk Panel, one of the most popular and stable control panels for Windows hosting, as free. You could also see the latest .NET framework, a crazy amount of functionality as well as Large disk space, bandwidth, MSSQL databases and more. All those give people the convenience to build up a powerful site in Windows server. ASPHostPortal.com offers DotNetNuke hosting starts from $5/month only. We also guarantees 30 days money back and guarantee 99.9% uptime. If you need a reliable affordable DotNetNuke Hosting, we should be your best choice.