E1: ORCH: Unable To Sign On To Orchestrator Studio Using JWT Token - 501 Not Implemented
(Doc ID 2884017.1)
Last updated on OCTOBER 02, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Unable to sign on to Orchestrator Studio using JWT Token
Customer setup a JWT token authentication for orchestrator studio and for the HTML server using Azure AD. The HTML login works as expected but the Orchestrator Studio login returns an error when browser is set to debug mode: 501 Not Implemented.
The redirect response type comes back as a POST and from troubleshooting the Orchestrator Studio login page does not support a POST request method as the HTML login page does.
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 |