My Oracle Support Banner

OUD 12c : How to Restrict Certain Attributes from Being Retrieved when Using Join or ForkJoin Workflow Elements with/without Join Participants or Remote DataSource(s) Like Active Direcotry or OID or ODSEE or OUD (Doc ID 3050480.1)

Last updated on OCTOBER 14, 2024

Applies to:

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

Goal

On : 12.2.1.3 or later version, For Proxy & Load-Balancing or OUD Virtualization Features (such as Join or ForkJoin WorkFlow Elements)

For this use case, the OUD proxy is configured with a backend Join Participant for Active Directory and Oracle Unified Directory Server.

It was observed when an ldapsearch was used to query any user attributes like "manager" and "email" provided two values which were from both remote datasources (AD and OUD). The ldapsearch command was issued from the OUD Proxy or OUD Instance that was configured with one of the previously mentioned WFE (workflow element).

 

 

In this use case, the OUD was the primary participant and the AD was the secondary participant.
The objective was to obtain the "manager" and "email" values from the AD, not from OUD.

Is it possible to have a setting to restrict or retrieve from, a specific backend/join participant for a given attribute?


 

Solution

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
Goal
Solution


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