In the DotNetNuke multi-portal environment, the Workontrol-PortalSSO enables single-sign-on account to login to multi-portals. Accounts created in one portal can be shared and used to login to other portals. Users will not need to remember multiple accounts to access different portals.
Feature highlights
- Custom login control supporting single sign on
- Real-time sharing of login accounts between portals (example: login to child portal using account from parent portal) upon login
- Login control can be placed on parent or child portal
- Configurable role-based page redirect for successfully login users
- Redirecting if usernames are in a defined role
- Supporting default page redirect if usernames not in defined role
- Supporting pre-authorizing accounts from one portal to access another portal
- allowing user role assignment before user login
How does it work?
DotNetNuke allows you to use a single hosting for multiple domain names. Each domain name can be setup as a parent portal. Child portals can be created as a sub URL from the parent portal. Figure 1 shows an example of an DotNetNuke hosting that supports two domains www.mysite.com and www.anothersite.com. Each parent domain has serveral child portals. Keep in mind that each portal, regardless of parent or child, has its own set of users/roles to control access the portal. The PortalSSO module enables each user in a single hosting for mulitple parent/child portals to login to all portals using a single sign-on account.

Figure 1 - DotNetNuke single hosting for multiple domain names
WorkControl-PortalSSO provides a login control that works similar the one in DotNetNuke. When users login via the PortalSSO login control, the module validates the username and password against a designated portal. This designated portal is specified in the module Settings page. If the account is valid, the module authorizes user to access the target portal. Table 1 contains screenshots of the module and their descriptions.
Table 1 - PortalSSO Screenshots
Additional Resources