Logon Tickets for Multiple Domains

In a default configuration, the portal system issues a single logon ticket for the domain of the portal system. Browsers only send the logon ticket to Web servers located in the same DNS domain as the issuer of the logon ticket. For example, if the portal is installed at server.example.com, the logon ticket is only valid for hosts in that domain, such as server1.example.com. Portal users can only access systems in that domain with Single Sign-On (SSO).

If you want to integrate applications that are located in various DNS domains in the portal and want to provide SSO with logon tickets to these applications, you need a separate logon ticket for every domain. For example, you set up a Business Intelligence system in your company's headquarters in the domain example.com, and a Customer Relationship Management system is installed in the domain example.ie. To enable SSO to applications running on these systems, the Web browser requires a separate logon ticket for both the domain example.com and example.ie.

By configuring the portal, it is possible to have logon tickets for several domains sent to the portal user's browser. For information about how to configure the portal, see Configuring Logon Tickets for Multiple Domains . For information about how the solution works, see How it Works .