The JSESSIONID is not Being Passed into the HTTP Header and the Request is Failed
Last updated on FEBRUARY 06, 2017
Applies to:Oracle Access Manager - Version 18.104.22.168.8 and later
Information in this document applies to any platform.
Using Linux Webgate version 22.214.171.124.0 and Apache 2.2.17
When hitting the application URL that's protected using SSO to login and access the main page, the JSESSION ID is not passed in the headers.
Although when disabling the webgate, the jsessionid is passed with no issue.
The JSESSIONID is passed in the Headers when the webgate is enabled and the flow works fine.
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