E1: XML Receiving Security Token Expired Even With Extended Token Set for 30 Days
(Doc ID 855371.1)
Last updated on DECEMBER 27, 2022
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Microsoft Windows (32-bit)
Configure DSI E1 client as trusted node
EnterpriseOne DSI OneWorld Function Caller client (Calls E1 C-APIs). The issue is that we are getting errors every 24 hours that the security token has expired when the DSI user tries to submit a request to E1. Yet the same E1 DSI user after getting the error from within DSI can sucessfully log into the E1 client with the same username and password.
What is causing this security token to expire only from DSI on the E1 client?
Errors in JDE Error logs:
3332/3336 MAIN_THREAD Thu Jul 02 06:31:58.109000 PSEOneAuthToken.cpp300
IsExpired: Token for user DSIUSER is expired
3332/3336 MAIN_THREAD Thu Jul 02 06:31:58.109001 PSEOneAuthToken.cpp163
IsValid: Token for user DSIUSER is expired
3332/3336 MAIN_THREAD Thu Jul 02 06:31:58.109002 PSAuthToken.cpp592
ValidateAuthToken: returning PSAUTHTOKEN_EXPIRED
3332/3336 MAIN_THREAD Thu Jul 02 06:31:58.109003 jdeksec.c4215
Failed to validate auth token: token expired
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document