400 Bad Request - For Oracle JET Application On JCS-SX With SSO User Context
Last updated on DECEMBER 20, 2017
Applies to:Oracle Java Cloud Service - SaaS Extension - Version N/A and later
Information in this document applies to any platform.
On : NA version, Managing Service Instances
400 Bad Request - for Oracle JET application on JCS-SX with SSO user context
Developed an Oracle JET web application hosted on Java Cloud Service – SaaS Extension as HCM cloud extension. The application integrates fine inside a new customized HCM page, but after we add security-constraint and login-config entries to the web.xml of our Oracle JET application (as suggested in https://cloud.oracle.com/developer/solutions?tab=tasks&solutionguid=OCPSI-GUID-119CCF5D-1C48-4B2E-996A-BEF1C0319D6C ) the Oracle JET app does not display in HCM page iframe, instead we see the following response payload:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<title>400 Bad Request</title>
<p>The request could not be understood by server due to
400 Bad Request
The request could not be understood by server due to malformed syntax.
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