While working with a customer using Oracle Unified Directory (OUD) as their LDAP directory, we noticed that OUD is not listed as part of the available "Server Type" options in Guardium for LDAP import.
Since OUD seems to implement Open LDAP as well, we selected that option and configured the rest of the required parameters with the information provided by the customer. When testing the import, Guardium is capable of getting a list of all the users in scope (according to the filter), but unfortunately it's not capable of reading their attributes (id, email, etc). Hence, those attibutes appear as "null" in Guardium.
After investigating the issue with support team they determined that this is the expected outcome considering the way OUD handles "ldapsearch" queries.
When using "Open LDAP" as Server Type, Guardium expects the "ldapsearch" query lying underneath to return all available attributes for any given user, but OUD seems to expect the query to specify which attributes you want to get (uid, email, etc.) If you don't specify the attributes, you only get the "isMemberOf" attribute, which is why Guardium displays the rest of attributes as "null".
According to support team, the logic to support UOD may be easy to implement in Guardium, since the behaviour of OUD looks similar to Open LDAP.
Do not place IBM confidential, company confidential, or personal information into any field.