Troubleshooting PeopleSoft Single Sign-On

3.9 Troubleshooting PeopleSoft Single Sign-On

To troubleshoot PeopleSoft Single Sign-On:

Check the license code.

Ensure that the license code is not blank. The WEBLIB functions that are used to access the PeopleSoft Interaction Hub Home page require a valid license code.

Query the database using an SQL query tool by running the following SQL against the database:
```
SELECT LICENSE_CODE FROM PSOPTIONS
```
Check the Message Nodes.
1. Ensure that the message nodes that exist on multiple PeopleSoft databases are the same.
  
  This means that the node name, the password, the PeopleSoft PeopleTools release, and the Application Release properties are an exact match in both the PeopleSoft Portal Solutions and the content provider database.
  
  Access the 8.5x Message Node definition online by selecting PeopleTools, Portal, Node Definitions.
  
  Query the database using an SQL query tool by running the following SQL against the database:
```
SELECT * FROM PSMSGNODEDEFN
```
2. Ensure that the PeopleSoft Portal Solutions database local default message nodes are inserted as trusted into all of the content provider databases that you are accessing by way of PeopleSoft Single Sign-On.
  
  Verify which Message Nodes are trusted in a PeopleSoft PeopleTools 8.5x database online by selecting PeopleTools, Security, Security Objects, PeopleSoft Single Signon.
  
  Query the database using an SQL query tool by running the following SQL against the database:
```
SELECT * FROM PSTRUSTNODES
```
3. Ensure that the content provider message node on the PeopleSoft Portal Solutions database has the correct Node Type.
  
  Ensure that the node is active.
  
  Content provider nodes for databases running on PeopleSoft PeopleTools 8.5x must have a Node Type of PIA.
  
  Verify the node information online by selecting PeopleTools, Portal, Portal Node Definitions.
  
  Select the Node Definition tab to view the Node Type and active status settings.
  
  Query the database using an SQL query tool by running the following SQL against the database:
```
SELECT * FROM PSMSGNODEDEFN
```
4. Ensure that the PeopleSoft Portal Solutions database default local node in the PeopleSoft Portal Solutions and content provider databases use password authentication and also use the same password.
  
  Because the password is encrypted when you enter it, you must re-enter the password in PeopleSoft Portal Solutions and all content provider databases. Be sure to use the same capitalization and verify that Caps Lock is not activated when you enter your password.
  
  To re-enter your password in the PeopleSoft Portal Solutions, select PeopleTools, Portal, Portal Node Definitions. Select the Node Definition tab.
  
  To re-enter your password in your content provider database running on PeopleSoft PeopleTools 8.5x, select PeopleTools, Portal, Portal Node Definitions. Select the Node Definition tab.
  
  Note:
  
  Messaging also uses the database local message node value. Changing the value of which message node is the Local Node affects both the portal sign-on and messaging.
Verify the content reference URL.
1. Verify the registry structure for the menu item (content reference). Ensure that the registry structure contains the correct syntax in the URL text for the PeopleSoft PeopleTools release of the content provider database.
  
  Access the registry structure by selecting PeopleTools, Portal, Structure and Content.
  
  In the Structure and Content page, select Portal Administration, Test and Single Sign-On. Edit the content provider (for example, "HRMS PT 8.5x User Profiles").
  
  In the URL information section, ensure that the Portal URL field, the URL text, menu, market and component are correctly displayed online.
  
  Run the following using your SQL query tool:
```
SELECT PORTAL_NAME, PORTAL_LABEL, PORTAL_OBJNAME, 
PORTAL_CNTPRV_NAM, PORTAL_URLTEXT FROM PSPRSMDEFN 
WHERE PORTAL_REFTYPE = 'C'
AND PORTAL_CNTPRV_NAM IN 
('BP','CRM','ELM','EPM','ERP','GFHA','HRMS','SA','SAHA','VAN')
AND PORTAL_LABEL = '<Fill in the link label you are testing>'
```
  The URL text for content references running on PeopleSoft PeopleTools 8.5x uses the following format:
  
  c/MAINTAIN_SECURITY.USERMAINT.GBL?ParamName=ParamValue
  
  For example: c/MAINTAIN_SECURITY.USERMAINT.GBL?TOOLS=840
2. Check the content provider URI text in the PeopleSoft Portal Solutions database.
  
  Access content provider URI text information by selecting PeopleTools, Portal, Node Definitions. Select the Portal tab to view content URI text.
  
  Query the database using an SQL query tool by running the following SQL against the database:
```
SELECT * FROM PSNODEURITEXT
```
  Verify that the content provider URI paths for databases with web servers on different machines utilize the full network domain name.
  
  Verify that the web server name used in the configuration.properties file and the content provider URI paths use the same capitalization format. This problem manifests itself as a web server error: "Unable to open page."
  
  See the section Updating the Content Provider URI Paths in this installation guide.
Verify the local node properties and uses.
1. Verify the local default node.
  
  The PORTAL_NAME for the local node must match the default portal in the PeopleSoft Portal Solutions database. The NODE_TYPE must be PIA.
  
  Query the database using an SQL query tool by running the following SQL against the database:
```
SELECT MSGNODENAME, LOCALNODE, LOCALDEFAULTFLG, NODE_TYPE, PORTAL_NAME FROM PSMSGNODEDEFN
```
  This problem manifests itself as an error: "Could not open registry."
2. Verify the Hosted by Node of the different portal registries.
  
  A local node should host each PeopleSoft Portal Solutions database portal registry. The PORTAL_REMOTE value should be set to 0.
  
  Query the database using an SQL query tool by running the following SQL against the database:
```
SELECT * FROM PSPRDMDEFN
```
  This problem manifests itself as an error: "Could not open registry."
  
  Note:
  
  This is the expected behavior for accessing any PeopleSoft PeopleTools 8.5x content provider homepage if you have set the PeopleSoft PeopleTools 8.5x content provider portal registry to be hosted by a remote node. In this case, access to the PeopleSoft PeopleTools 8.5x content provider is achieved only through the PeopleSoft Interaction Hub.
Verify use of different web server HTTP port numbers.

The browser may have an issue with PeopleSoft Single Sign-On in the following scenario:

The PeopleSoft Portal Solutions database and the content provider database are using the same web server, but the content provider database web server configuration has a different HTTP port; http://myserver:5000/, for example.

To resolve this issue, do one of the following:
1. Move one of the web servers to a different machine.
2. Add a second DNS entry for the web server and use a different name.
  
  Ensure that the two DNS entries share a common domain and set the authtokendomain in the configuration.properties file for the web server accordingly.
3. Set the defaultPort setting in the configuration.properties file on the content provider web server to the HTTP/HTTPS port value on which the web server is running.
  
  Normally, if you are not using a reverse proxy server or SSL accelerator, you do not need to set the defaultPort property. However, it can be set in this situation.
Verify the Content and Portal URI text in the content provider database for the Registry Node.

If you are able to access the content provider using the User Profile test links, but your pagelets are not displaying correctly, you must configure the Content and Portal URI text in the content provider database for the Registry Node.
Verify that your webserver has an Authentication Token Domain. For example, us.oracle.com
Ensure that the content provider node configured on the Portal Solutions database is the same one as specified below:
1. Navigate to Portal Administration, Navigation, Structure and Content
2. Select Portal Administration, Test, Single Sign-On, and Edit for the application you are using as content provider. The Node Name field has the node name used to access that content provider.