I’m trying to connect a third-party software to Active Directory via LDAP(S). Because our domain is covered by a bunch of domain controllers and some are not accessible by the entire domain, service discovery is important. That, however, seems to contradict the SSL options of JNDI.
What I’ve tried so far are the following provider urls:
<code># Uses DNS with round-robin, which does not respect SRV priority
ldaps://example.com:636
# Connects via port 389, which is not desired
ldap:///dc=example,dc=com
# Does not seem to work as it also uses port 389
ldaps:///dc=example,dc=com
</code>
<code># Uses DNS with round-robin, which does not respect SRV priority
ldaps://example.com:636
# Connects via port 389, which is not desired
ldap:///dc=example,dc=com
# Does not seem to work as it also uses port 389
ldaps:///dc=example,dc=com
</code>
# Uses DNS with round-robin, which does not respect SRV priority
ldaps://example.com:636
# Connects via port 389, which is not desired
ldap:///dc=example,dc=com
# Does not seem to work as it also uses port 389
ldaps:///dc=example,dc=com
Is there any way to use service discovery and at the same time force the usage of the TLS port 636? Adding LDAPS SRV records is not really an option according to my domain admin.