Skip to main content

Hi,

 

we are trying to set up AD synchronization to a customer’s IFS APPS10. The connection however returns the error Simple bind failed

 

 

Now there is a thread about this we found (Certificate LDAPS for Active Directory IFS 10 | IFS Community), that suggests the following:

 

1. because SSL is not working.

=> We have installed the LDAP server’s certificate on the IFS server and we also followed this document Secured Communication (ifs.com) to install the certificate to a java truststore following the section Importing a certificate to a 3pp java truststore.


2. because the password entered is wrong.
3. because the port is not open.

=> We have tested the connection successfully using Microsoft’s ldp.exe, so the port and credentials are correct.

Hi @Mikko1234 

 

Did You check this?

 


Hi,

 

I just tested this, and that verification gave success:

 

To clarify further, we have Azure AD set up as identity provider, but we are trying to set up the user synchronization to the on-premises AD ldap server.


Hi @Mikko1234,

Try below steps and check the issue is getting fixed.

Steps

-------

1. Login to IFS Middleware Admin Console.

2. Then navigate here "Common -> Security -> Integrations & Compatibility".

3. In the "Active Directory Authenticator" fill until "New Password" field. Don't fill "User Base DN and Group Base DN" (If you are using LDAPS (Port 636) then you need to tick “Use SSL”).

4. Then press "Verify AD TLS".

5. Then you will get a window asking keystore password.

6. After providing the password please give a full restart to the IFS Servers.

 

FYI – Please do this in a downtime as we have to restart the services.

By doing above steps our middleware will fetch the AD certificate automatically and import to the keystore.

Thank You,