Hello everybody, has anybody succeeded in using the JNDI provider with an SSL implementation not originating from netscape ?
I tried setting the property "java.naming.ldap.factory.socket" to "netscape.ldap.factory.JSSESocketFactory" as this class was described as doing exactly what I want - the problem is that the property value is not being interpreted as the name of the socket factory but as the name of the socket implementation itself. I'm having the impression either this property isn't suitably named or I'm looking for a property with another name. Greetings, Robert Skarwecki
