Utilizing the Network Domain Name

3.2 Utilizing the Network Domain Name

PeopleSoft Single Sign-On is implemented using browser cookies. Consequently, you must configure the web server so that your browser sends the Single Sign-On cookie to each web server machine to which you require Single Sign-On access. By default, the browser only sends cookies back to the machine that set the cookie.

Note:

Perform this task only if the web servers for your PeopleSoft Portal Solutions database and any single content provider database reside on different machines.

For databases whose web servers reside on different machines, you must utilize the network domain name in the web server configuration. Extend the localhost name to include the full domain name. You can do this by appending the domain name to the hostname of the web server machine name. For example, assume the following:

The PeopleSoft Portal Solutions web server machine localhost name is myserver1.
The content provider web server machine localhost name is myserver2.
The network full domain name is mydomain.com.

If web server myserver1.mydomain.com sets a cookie (when you enter your ID and password into the sign-on page of the PeopleSoft Portal Solutions web server myserver1), then the browser only sends the cookie back to myserver1.mydomain.com. The browser does not send the cookie to myserver2.mydomain.com. To have the browser send the Single Sign-On cookie to all servers in the network domain, you must use the Authentication Token Domain.

Note:

If your web server, myserver, has a static IP address and an entry in the Domain Name Server (DNS), then you can access the localhost value of myserver.mydomain.com (network domain name) by way of a browser.

Without a DNS entry, browsers in the network domain can access the PeopleSoft Portal Solutions database only if the browser machine Hosts file includes a line that specifies the IP address of the PeopleSoft Portal Solutions web server machine.

See PeopleTools: Portal Technology.

See PeopleTools: Security Administration.

Note:

When using the network domain name, you must set the Authentication Token Domain for the PeopleSoft Portal Solutions database and the accessed content provider databases. You can do this by specifying an Authentication Token Domain during the PeopleSoft Pure Internet Architecture setup. Alternatively, you can adjust the Authentication Domain property on the General tab of the Web Profile Configuration page by selecting PeopleTools, Web Profile.

See the information on setting up the PeopleSoft Pure Internet Architecture in the PeopleTools installation guide for your database platform and current PeopleTools release.

See PeopleTools: Portal Technology.

Note:

When setting the Authentication Token Domain in the content provider database web server configuration, the content provider URL path in the PeopleSoft Portal Solutions database must include the network domain name as part of the localhost value. Refer to the task “Updating the content provider URI Paths" in this chapter.

Note:

When setting the Authentication Token Domain in the PeopleSoft Portal Solutions database web server configuration, the browser URL address must include the network domain name as part of the localhost value.

See the section Testing PeopleSoft Single Sign-On in this chapter.