My Oracle Support Banner

OUD 12c Proxy to AD: OUDSM and WebCenter (WC) Return Binary Non-ASCII Value for objectGUID Attribute Causing Broken Historical Data/Images Displayed in WC (Doc ID 2970223.1)

Last updated on AUGUST 28, 2023

Applies to:

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


Oracle Unified Directory (OUD) 12c setup as a proxy to backend Microsoft (MS) Active Directory (AD) LDAP server, for example configured as per Steps 0 and 1 from:  OVD to OUD - A Practical Guide with Examples to Create Similar OVD Adapters in OUD Proxy (Doc ID 2758572.1).

Issue 1:

Oracle Unified Directory Services Manager (OUDSM) export of AD-proxied entries to ldif file shows their objectGUID values as binary.

Equivalent ldapsearch commands output of the same users return yet other different values for their objectGUID's.

For example:

The objectGUID for a test user using ldapsearch command shows:

Already verified/confirmed the latest OUD Bundle Patch required (OUD BP or higher) is applied as per:

OUD 11g / 12c - Proxy Does Not Transform the Orclguid to Objectguid Value on Search (Doc ID 2320763.1) (which includes the fix for Enhance Request (ER) Enh 26963341 - oud11g - er proxy does not transform the orclguid to objectguid value on search).




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.