OAM Diagnostic Log Reports "Exception in parsing Obrareq request" and "Partner <AGENT_ID> not registered"
(Doc ID 2708122.1)
Last updated on SEPTEMBER 21, 2023
Applies to:
Oracle Access Manager - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On OAM 12.2.1.3.0 or later, during normal operation the following warnings are encountered in the OAM diagnostic logs:
- It is noted that the <WEBGATE_AGENT_NAME> in the message above matches one of the agents in OAM, but the case does not match.
- Example: instead of Agent_Name the Partner value reported in the error message is agent_name.
- There is no reported loss of functionality from end users associated with the error messages.
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |