Understanding Single Signon Options
Single signon refers to the ability of users to navigate freely within a system of multiple applications after only being authenticated once. There are three different ways to configure single signon, depending on the participating applications that you have installed. The following table displays the single signon options.
| Single Signon Option | Description |
|---|---|
|
PeopleSoft-only |
This option enables single signon only between multiple PeopleSoft applications, such as PeopleSoft Human Capital Management and PeopleSoft Customer Relationship Management. After a user is authenticated by one PeopleSoft application, an in-memory value gets set in the browser (PS_TOKEN cookie) that the next PeopleSoft application uses for a user credential. If you have only PeopleSoft applications, use this option. Note: This option is the same single signon feature offered in previous PeopleSoft releases. |
|
PeopleSoft and Oracle applications |
If you have Oracle applications and PeopleSoft applications being used in your organization, users who have been authenticated by the Oracle system can freely access PeopleSoft applications without having to be re-authenticated. This option is tailored for sites running their PeopleSoft applications on Oracle WebLogic . This option applies to all previous PeopleTools 8.x versions. For example, if you intend to incorporate applications running on Enterprise PeopleTools 8.53, you can implement this option. See Implementing Oracle Access Manager as the PeopleSoft Single Signon Solution. See Implementing OCI-IAM as the PeopleSoft Single Signon Solution. |
Note:
You must ensure that before users attempt to use the single signon functionality, a valid user profile is defined for each user in each participating application database. You can accomplish this in a variety of ways, such as automatically generating user profiles based on users' LDAP information, replicating user profiles through Integration Broker at initial sign in, or manually defining user profiles for the authorized users before going live.
Note:
Many single signon solutions require that you create a generic user profile with minimal permissions and set up this user as the default or public access user. You find information for creating the public access user profile in this documentation. You find information for specifying the identity of the public access user in the product documentation for PeopleTools: Portal Technology.