Oracle Access Manager (OAM 12c) Diagnostic Log Files Show Different Values for Header Responses When User Attribute is Absent and Trace Levels are Different (Doc ID 2457253.1)

Last updated on OCTOBER 18, 2023

Applies to:

Oracle Access Manager - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

Oracle Access Manager (OAM 12c) Diagnostic Log Files Show Different Values for Header Responses When User Attribute is Absent and Trace Levels are Different

OAM response is set for an LDAP attribute value.
For those use cases when the value is not present in LDAP it should set/return "NOT_FOUND"
This is only the case if the OAM Diagnostic file TRACE: is set to any value below 16
When OAM TRACE:16 or higher is set it set/returns "NULL"

Example

OAM_LOG LEVEL :- Notification:1-15

As per application specific requirement this HTTP Header value is being used. When the described scenario is present the expected value should be "NOT_FOUND". If the value is passed differently by the OAM (based -n TRACE LEVEL), the application cannot process this value
Did not have this issue with OAM 11.1.2.2.x

Changes

OAM Logger configured for value 16

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

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

Oracle Access Manager (OAM 12c) Diagnostic Log Files Show Different Values for Header Responses When User Attribute is Absent and Trace Levels are Different (Doc ID 2457253.1)

Applies to:

Symptoms

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!