E1: ORCH: After Changing the _GLOBALNODE Timeout, Still Getting " Invalid Token: Please Request a New Token" Error Every 12 Hours
(Doc ID 2811353.1)
Last updated on SEPTEMBER 30, 2021
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Due to the Token Expiration issue, you have increased the timeouts for _GLOBALNODE (E1: ORCH: How to Setup a "_GLOBALNODE" in E1 to Work With JWT trust Using Orchestration/AIS (Doc ID 2758273.1). However, the token related error shows up in the AIS server log every 12 hours. Scheduler is up and running and all the scheduled jobs are working as expected. Why there are multiple token invalid error in the AIS log?
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |