UnboundID na iya sanya LDAPS cikin ramin HTTP CONNECT
Yi amfani da HTTPProxySocketFactory tare da masana'antar soket ta TLS kuma yi la'akari da rashin goyon bayan tantancewar wakili kai tsaye.
UnboundID LDAP SDK 7.0.5 yana ba da HTTPProxySocketFactory don hanyar HTTP CONNECT. Bayar da masana'antar soket ta TLS na aikace-aikacen lokacin da makomar ita ce LDAPS:
var proxyFactory =
new com.unboundid.util.HTTPProxySocketFactory(
"proxy.example.net", 8080, 10000, ldapsTlsFactory);
ldapsTlsFactory ita ce SSLSocketFactory na aikace-aikacen tare da tsarin amincewar uwar garken da ake so. Miko proxyFactory ga maginin LDAPConnection wanda ke karɓar masana'antar soket da ainihin sunan uwar garke da tashar jiragen ruwa na uwar garken LDAP.
Har ila yau, saita tabbatar da sunan uwar garken na haɗin. SDK yana bayyana HostNameSSLSocketVerifier ta LDAPConnectionOptions; amincewa da mai fitar da takardar shaidar kawai ba daidai ba ne da daidaitawa da uwar garken LDAP da ake so.
Dole ne wakilin HTTP ya ba da izinin CONNECT zuwa wannan makomar, sau da yawa tashar 636 don LDAPS. Wakili da aka iyakance ga tashoshin makomar yanar gizo na iya ƙi shi.
Dokokin da aka rubuta na masana'antar suna da mahimmanci: sadarwa zuwa wakilin kansa ba a ɓoye ta da TLS ba, kuma ba ya ba da goyon baya kai tsaye ga tantancewar wakilin HTTP. Bayar da masana'antar TLS ta LDAPS yana kare haɗin jagorar da ke zuwa, maimakon ƙara hanyar shiga wakili da ta ɓace.