My Oracle Support Banner

400 Bad Request - For Oracle JET Application On JCS-SX With SSO User Context (Doc ID 2306555.1)

Last updated on JUNE 06, 2018

Applies to:

Oracle Java Cloud Service - SaaS Extension - Version N/A and later
Information in this document applies to any platform.

Symptoms

400 Bad Request - for Oracle JET application on JCS-SX with SSO user context

Oracle JET web application is developed and hosted on Java Cloud Service – SaaS Extension as HCM cloud extension. The application integrates fine inside a new customized HCM page, but after security-constraint and login-config entries to the web.xml is added to 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 following response payload is seen:

 


ERROR
-----------------------
400 Bad Request

The request could not be understood by server due to malformed syntax.

 

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!


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