LDAP Provider In OAM 12c Not Connecting To AD LDAP
(Doc ID 2480432.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Identity Store Access
LDAP Provider in OAM 12c not connecting to AD LDAP
OAM was configured and working with SSL. You use a 2016 AD servers as a authentication provider for logging in to OAM. For security reasons the AD server was configured to communication only using TLS 1.2 protocol. When going into the Weblogic console then
after configuring OAM for TLS 1.2 only we are seeing these errors in the logs on AdminServer startup:
<Nov 28, 2018 12:45:46,775 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/oracle/Oracle/Middleware/wlserver/server/lib/CustomTrust.jks.>
<Nov 28, 2018 12:45:46,879 PM EST> <Warning> <Security> <BEA-099117> <The LDAP authentication provider named "ADWolftechAuthenticator" failed to make a connection to LDAP server at ldaps://my-dev-dc.oracle.com:636, the error cause is: Connection reset by peer.>
Go to Weblogic console then Security Realms -> myrealms -> Providers
Select 1 of the AD LDAP providers
ADWolftechAuthenicator then Provider Specfic
When click lock and edit and try to save you get this error in the weblogic console:
[Security:090834]No LDAP connection could be established. ldaps://my-dev-dc.oracle.com:636 Cannot connect to the LDAP server
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