Coherence Web Session Gets Invalidated In Authenticated Context
Last updated on SEPTEMBER 27, 2017
Applies to:Oracle Coherence - Version 3.7.1 and later
Information in this document applies to any platform.
When application transitions from non-authenticated context to an authenticated context, the original Coherence Web HTTP session gets invalidated, a new, empty session is created, and a new jsessionid cookie is sent to the browser. When the same applications do not use Coherence, the applications are able to share the same jsessionid cookie.
Why does the transition from non-authenticated to authenticated context causes a new cookie to be created when using coherence?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms