E1: ORCH: Orchestrator Scheduler Fails to Auto-start During AIS Instance startup with Error - "KSEC0000400 - Failed to authenticate user for token: eSecInvalidToken: The security token is invalid" - in the Security Kernel Log (Doc ID 2963852.1)

Last updated on MAY 14, 2024

Applies to:

JD Edwards EnterpriseOne Orchestrator - Version 9.2 and later
JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Orchestrator Scheduler does not auto-start after AIS server has been stopped and restarted. Also, the Health Check for the AIS instance was not successful for JWT Trust Login. AIS instance's debug log at the time of the instance startup captures below messages:

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

E1: ORCH: Orchestrator Scheduler Fails to Auto-start During AIS Instance startup with Error - "KSEC0000400 - Failed to authenticate user for token: eSecInvalidToken: The security token is invalid" - in the Security Kernel Log (Doc ID 2963852.1)

Applies to:

Symptoms

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!