Set the SSO domain name

Domain name types

Single SSO Domain	One domain name for all single sign-on hosts. For example, for system test4, registered as part of the myco.com network domain, the fully qualified host name is... test4.myco.com If SSO is enabled for the myco.com domain, only cookies that originate in this domain are authenticated and can be stored on test4.myco.com.
Blank	Use local host as SSO Domain. The Web browser defaults the domain name to the host name where the web application is running. Single sign-on is then restricted to the appserver host name and does not work with other appserver host names in the domain.
Multiple SSO domains	Specify multiple domains using a semicolon (;), space ( ), comma (,), or pipe (|). The host name of each HTTP request is compared with each domain until the first match is located. For example, if you specified... myco.com;prod.myco.com ...as the SSO domain names and a match is found in the myco.com domain first, the appserver does not try to find a match in the domain If a match is not found in either myco.com or prod.myco.com, the appserver does not set a domain for the Ltpa Token cookie.
Arbitrary SSO domain	Use URL domain as SSO domain. If we enter... UseDomainFromURL in the Domain name field, the appserver sets the SSO domain name value to the domain of the host used in the web address. For example, if an HTTP request comes from... server1.myco.com ...the appserver sets the SSO domain name value to... myco.com UseDomainFromURL is not case-sensitive. We can enter usedomainfromurl.

Set the SSO domain name

1. Log on to the WAS console on the dmgr.

2. Select...
   Security | Global security | Web and SIP security | Single sign-on (SSO)

3. Enter a value for the SSO Domain name.

4. Click Apply and then click Save.

5. Perform a full synchronization of all the nodes.

What to do next

Use available authentication data when an unprotected URI is accessed

Parent topic:
Configure single sign-on

Related:
Set up federated repositories