E-IB : 'PSFT Authentication token failed for Node %1' when Pinging Remote Node

(Doc ID 652765.1)

Last updated on NOVEMBER 14, 2017

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
Applies To: PeopleTools 8.48 and higher releases

This document was previously published as Customer Connection Solution 201033814


***Checked for relevance on 05-JUL-2010***
***Checked for relevance on 06-DEC-2016***


Symptoms

Scenario 1:

--------------


Local default node pings okay, but remote node (for another PeopleSoft environment) produces the error Authentication token failed  

Example:
HRMS and Financials environments.  HRMS environment has a local default node called PSFT_H9DEM.  Local default node PSFT_H9DEM pings ok.     In the HRMS environment, there is a remote node called PSFT_F9DEM for the financials environment.   When pinging remote node via the PIA browser,  get the following error message:
 " PSFT Authentication token failed for Node PSFT_H9DEM"  

In the HRMS Application server Log, the message is :

PSAPPSRV.2080 (57) [01/22/07 13:47:34 CNYPRCS@JavaClient
IntegrationSvc](3) PeopleSoft Token authentication failed: issuing node
PSFT_F9DEM is not a trusted node : UPG@JavaClient

Scenario 2:

------------

A synchronous service operation being published from PSFT_EP to PSFT_HR failed with the error message, 'PSFT Authentication token failed for Node %1'.  The issue was resolved after adding PSFT_EP Node as a trusted node in HCM.

 

Scenario 3:

------------

When attempting to Ping remote node in Portal database - the following error occurs:

Asynchronous Message Handler: Access denied. Target and source message node passwords do not match

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms