In this use case, an unauthenticated user first accesses a protected resource in the DNS Domain 2, the non-primary domain. The user then accesses a protected resource in the primary domain, DNS Domain1.
An unauthenticated user attempts to access a resource in Domain 2. Example: http://Host2.Domain2.com:80/app2/test2.html.
The policy agent intercepts the request and receives no SSO Token.
Because CDSSO is enabled, the policy agent responds with a redirection to the OpenSSO Enterprise CDC servlet URL https://serverHost1.Domain1.com:8443/opensso/cdcservlet.
The browser follows the redirection to access the CDC servlet without any SSO token. The CDC servlet responds with a login page.
The user types his credentials on the login page and clicks Submit.
A login form is posted to the OpenSSO Enterprise server.
If the user authenticates successfully, the OpenSSO Enterprise responds by setting an SSO token in Domain1.com.
The response also redirects the browser back to the CDC servlet https://serverHost1.Domain1.com:8443/opensso/cdcservlet.
The browser follows the redirection to access the CDC servlet again.
This time the SSO token is sent in the HTTP request because the OpenSSO Enterprise server DNS domain matches the cookie domain.
The CDC servlet validates the SSO Token and responds with an HTML page.
The page contains an HTML form which is automatically posted to CDSSO Redirect URL on the policy agent http://Host2.Domain2.com:80/agentapp/sunwCDSSORedirectURI. The form's hidden field LARES is an encoded Liberty-like AuthnResponse that contains the existing SSO Token in Domain1.
The browser automatically posts the form with LARES to http://Host2.Domain2.com:80/agentapp/sunwCDSSORedirectURI with no user interaction.
The policy agent responds by setting a second SSO Token. The second SSO token domain is the policy agent's fully-qualified host name. The cookie value is identical to the cookie value set by the OpenSSO Enterprise server in step 4. The HTTP response also redirects the browser to the original requested resource http://Host2.Domain2.com:80/app2/test2.html.
The browser follows the redirection to access the protected resource again at http://Host2.Domain2.com:80/app2/test2.html.
The second SSO Token is sent to the policy agent.
The policy agent validates the SSO token, and evaluates the policies.
The policy agent, upon successful validation, responds with the content of the protected resource.
The user now attempts to access a resource in the primary domain, Domain 1. Example: http://Host1.Domain1.com:7001/app1/test1.html.
An SSO Token is sent with the HTTP request. The browser now has two SSO Tokens, one for each domain. The sent token was obtained in Step 4.
The policy agent intercepts the request and receives the SSO Token.
The policy agent validates the token and permits the server to serve the content of the protected page.