Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Single sign-on settings
Use this page to set the configuration values for single sign-on (SSO).
To view this admin console page...
- Click Security > Global security.
- Under Authentication, click Web and SIP security > Single sign-on (SSO).
New feature: The Set security cookies as HTTPOnly to resist cross-site scripting attacks check box has been added to the Single sign-on settings page for this release. The HttpOnly attribute is a browser attribute created to prevent client side applications (such as Java scripts) from accessing cookies to prevent some cross-site scripting vulnerabilities. The attribute specifies that LTPA and WASReqURL cookies include the HTTPOnly field.New feature:
Enabled
Specifies that the single sign-on function is enabled.
Web applications that use J2EE FormLogin style login pages, such as the admin console, require single sign-on (SSO) enablement. Only disable SSO for certain advanced configurations where LTPA SSO-type cookies are not required.
Data type: Boolean Default: Enabled Range: Enabled or Disabled
Requires SSL
Specifies that the single sign-on function is enabled only when requests are made over HTTPS SSL connections.
Data type: Boolean Default: Disable Range: Enable or Disable
Domain name
Domain name (.ibm.com, for example) for all single sign-on hosts.
The application server uses all the information after the first period, from left to right, for the domain names. If this field is not defined, the web browser defaults the domain name to the host name where the web application is running. Also, single sign-on is then restricted to the application server host name and does not work with other application server host names in the domain.
We can specify multiple domains separated by a semicolon (;), a space ( ), a comma (,), or a pipe (|). Each domain is compared with the host name of the HTTP request until the first match is located. For example, if you specify ibm.com;austin.ibm.com and a match is found in the ibm.com domain first, the application server does not match the austin.ibm.com domain. However, if a match is not found in either ibm.com or austin.ibm.com, then the application server does not set a domain for the LtpaToken cookie.
If you specify the UseDomainFromURL value, the application server sets the SSO domain name to the domain of the host used in the web address. For example, if an HTTP request comes from server1.raleigh.ibm.com, the application server sets the SSO domain name to raleigh.ibm.com.
Tip: The UseDomainFromURL value is case insensitive. We can type usedomainfromurl to use this value.
Data type: String
Interoperability mode
Specifies that an interoperable cookie is sent to the browser to support back-level servers.
In WAS, v6 and later, a new cookie format is needed by the security attribute propagation functionality. When the interoperability mode flag is enabled, the server can send a maximum of two single sign-on (SSO) cookies back to the browser. In some cases, the server just sends the interoperable SSO cookie.
Web inbound security attribute propagation
When web inbound security attribute propagation is enabled, security attributes are propagated to front-end application servers. When this option is disabled, the single sign-on (SSO) token is used to log in and recreate the Subject from the user registry.
If the application server is a member of a cluster and the cluster is configured with a data replication service (DRS) domain, then propagation occurs. If DRS is not configured, then the SSO token contains the originating server information.
With this information, the receiving server can contact the originating server using an MBean call to get the original serialized security attributes.
Set security cookies as HTTPOnly to resist cross-site scripting attacks
The HttpOnly attribute is a browser attribute created to prevent client side applications (such as Java scripts) from accessing cookies to prevent some cross-site scripting vulnerabilities. The attribute specifies that LTPA and WASReqURL cookies include the HTTPOnly field.
For session cookies, see the session settings for servers, applications, and web modules.
Data type: boolean Default: enabled Range: enabled or disabled
Configure single sign-on capability with Tivoli Access Manager or WebSEAL
Related
Login module settings for JAAS
SecurityConfigurationCommands command group
Internet Explorer Does Not Set a Cookie for Two-Letter Domains