There are some instructions on the internet floating around in order to integrate the OEM 13c (or basically Weblogic 12c) and OEM 13c with Microsoft Active Directory/LDAP.
However in our case things went not as smoothly as advertised (Duh!). We have two OEM installations (OEM 12c and OEM 13c) in our company, but using the same AD. One would expect to just copying the settings from the working installation (OEM 12c) to the new OEM (13c) and everything would be peachy..Alas…This was not so much what was happening on our site.
With the aid of Oracle Support (credit where credit is due!) we (they) where able to solve this issue..
Both for future reference and documentation I’m sharing the settings we needed to set to make the stack play together nicely..
I’m not going to re-write the excellent instructions provided by oracle with the video located here: Oracle AD instructions
When following the above instruction don’t work, continue with my experiences as a last resort before contacting Oracle Support..
Start with the basics and open the WebLogic Console in the browser:
The key is in the configuration parameters used (once again: duh!). Below are the settings which worked for our site:
*note* anything NOT mentioned should be either default, or the same as in the tutorial video from oracle
restart OEM with:
./emctl stop oms -all -force
./emctl start oms
This is what did it for us, hope it helps.
If not in your case…revert to Oracle Support or Google some more 😉