Oracle Access Manager 11g R2PS3 (OAM 11.1.2.3): POST Data Preservation Does Not Work When POST Data Is Larger Than 5000 Bytes
(Doc ID 2332484.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.3.170117 to 11.1.2.3.171017 [Release 11g]Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Symptoms
Using POST Data Preservation and Restoration to make sure POST data gets restored when session is in idle timeout before submit.
This works for small payloads but it fails when POST data is roughly 5000 KB large. POST data is lost on re-authentication, after either token validity period expires at WebGate side, or idle session timeout.
A blank page is displayed.
Changes
Enabled POST Data Restoration (set PostDataRestoration=true) and increased the following parameters in the Agent/WebGate user-defined parameters:
MaxPostDataBytes=80000
MaxPreservedPostDataBytes=80000
ChallengeRedirectMaxMessageBytes=80000
so that POST data is not exceeding the limit.
Still, POST data is not preserved.
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 |