LDAPS uses port number :either 636 or 3269
Please follow instruction:
http://metaintegration.net/Products/MIMM/MIMMReadme.html#SSL
In LDAP Authentication, the user password is not managed by the software and is simply passed through to the LDAP system.
Note: this password is not encrypted when communicated between the client and the server. Thus, in order to ensure encryption you may wish to specify HTTPS protocol communication, as above.
Note: this password is also not encrypted when communicated between the server and LDAP. Thus, in order to ensure encryption you may wish to also specify LDAPS protocol communication and thus use SSL to encrypt.
In order to support LDAPS, the MIMM Tomcat service does not itself need to be configured to work with LDAPS for encryption of passwords. However, to enable secure SSL communication between MIMM and LDAP servers the Administrator needs to import the trusted certificate that the LDAP server is using into the JRE that the MIMM Application server is using. The following page describes the process: http://docs.oracle.com/javase/tutorial/security/toolsign/rstep2.html.
The command looks like the following:
cd %MIMM_HOME%\jre\lib\security
..\..\bin\keytool.exe -importcert -alias john -file YourOwnCertificate.cer -keystore jssecacerts
This is an entirely different certificate from the one used by the HTTPS protocol.
