The
PS_TOKEN is generated using either the database's SSL Certificate or User ID,
Language Code, Timestamp, Issuing System Default Local Node, Default Local Node
Password which is encrypted using SHA1_Hash
Configuration for Single Signon:
1) The
Default Local Node of one system must match in Name and Password to a Remote
Node on the second system. The reverse is also true; the Default
Local Node of the second system must be represented with a Remote node of
identical Name and Password on the first system. This is a basic
trust relationship model.
2) The AuthTokenDomains must match between systems. This means that the following must be consistent:
a)
Authentication Domain in the General Tab of the Web Profile must be set
b)
CookieDomain session parameter value must be set in the
%PS_HOME%\webserv\sitename\applications\peoplesoft\PORTAL\WEB-INF\weblogic.xml
file.
c)
URI values on all nodes involved must include the fully qualified domain name,
not simple machine names.
3) If
systems use the same web server, defaultPort and defaultScheme must be set on
the configuration.properties. The Protocol and Port must be set on
the Virtual Addressing tab of the Web Profile.
4) Nodes MUST use passwords or an SSL certificate.
5) The Nodes (both the Default Local and Remote node) must be trusted in all databases.
6) User ID must exist with same name (not necessarily same password) in both systems.
Note:
Portal and
Content webservers should have unique Session Cookie Names. If you are
integrating portal with other application
