My Oracle Support Banner

OUD11g / 12c During Startup the OUD Proxy Marks the Extension as Down with "Result Code: 48 (Inappropriate Authentication)" On LDAP Data Source (Doc ID 2351408.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Unified Directory - Version 11.1.1.5.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to integrate an external LDAP Server with OUD Proxy, error responses from the backend directory due to the nature of the OUD monitoring Bind request. Example error below is from OpenLDAP Server.

ERROR
-----------------------
The simple bind attempt failed
Result Code:  48 (Inappropriate Authentication)




The issue has the following business impact:
Due to this issue, OUD Proxy marks the backend directory as 'DOWN', even when the backend directory is available to connect to from the same host as the OUD proxy

Changes

If LDAP server is restricted for anonymous binds, OUD is considering the extension as down even with proper bindDN and bindPass configurations. 

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


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