<div dir="ltr">On Fri, Nov 1, 2013 at 10:48 AM, Byte Flinger <span dir="ltr"><<a href="mailto:byteflinger@gmail.com" target="_blank">byteflinger@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><p>And I am guessing there is no way to change that in a simple way like you can do with login.config file without rewriting a whole new connector? If that's the case then it unfortunately makes the suggestion above invalid since we'd still have to add the certificates to the java store.</p>
</blockquote><div><br></div><div>I suggested using ldaptive for JAAS because vt-ldap needs to use a singleton to store the SSLContext configuration for your use case and I didn't want it stomping on the resolver configuration.</div>
<div>Try adding this to your resolver configuration:<br></div><div><br></div><div><div><LDAPProperty name="edu.vt.middleware.ldap.ssl" value="true"/></div><div><LDAPProperty</div><div> name="edu.vt.middleware.ldap.sslSocketFactory"</div>
<div> value="edu.vt.middleware.ldap.ssl.SingletonTLSSocketFactory{edu.vt.middleware.ldap.ssl.KeyStoreCredentialConfig{{trustStore=file:/path/to/my/truststore}}}"/></div></div><div><br></div><div>and then use the ldaptive JAAS configuration I posted earlier.</div>
<div>This should allow you to configure truststore locations for both login and attribute resolution.</div><div><br></div><div>--Daniel Fisher</div><div><br></div></div></div></div>