LDAPS Configuration

NorbertBaumann

Hello,

I need a way to route authentication credentials through LDAPS instead of LDAP.

Customers have made changes in their security departments and now require all communication to go through LDAPS.
Initially, we tried blocking the LDAP port, but unfortunately that caused ANAPLAN XL to fail.

However, this is such a critical issue for customers that the product is now being called into question and go-lives are being postponed.

I would like the option to specify two parameters in web config file one for the LDAP server and one for the port, or a combination of both.

Something like that:
<configuration>
<connectionStrings>
<add name="ADConnectionString" connectionString="LDAPS Server with Port"/>
....

Thank you and best regards,
Norbert

Dan682Lee

To route authentication through LDAPS instead of plain LDAP, you’ll need to adjust the connection string so it specifies the secure protocol and port (usually 636). In practice, this means updating your configuration file to point to the LDAPS server and port explicitly, for example:
<configuration>
<connectionStrings>
<add name="ADConnectionString"
connectionString="LDAP://yourserver:636/DC=domain,DC=com" />
</connectionStrings>
</configuration>

Key points to check:

• Ensure the LDAP server is configured to accept LDAPS connections and has a valid SSL certificate.
• Verify that your application or middleware supports LDAPS (some libraries require enabling SSL explicitly).
• Test connectivity with tools like ldp.exe or openssl s_client to confirm the secure bind works.
  This way, you can meet customer security requirements without breaking functionality. If ANAPLAN XL failed when you blocked the LDAP port, it likely means the client wasn’t configured to use LDAPS yet—so updating the connection string and confirming SSL support should resolve it.