[
https://issues.apache.org/jira/browse/QPID-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732773#comment-13732773
]
Rob Godfrey commented on QPID-4463:
-----------------------------------
So... in psuedo-code I would expect the LDAP Auth manager to be doing something
like:
{code}
Class<? extends AbstractLDAPSSLSocketFactory> clazz =
AbstractLDAPSSLSocketFactory.getSubClass(getName()); // we may need to
ensure the name
// would be a valid
Java class name
SSLContext sslContext = generateSSLContext(); // where generateSSLContext()
creates an
// SSLContext from the TrustStore
AbstractLDAPSSLSocketFactory.setSSLContext(clazz.getName(), sslContext);
env.put("java.naming.ldap.factory.socket", clazz.getName());
{code}
> SimpleLDAPAuthenticationManager should accept truststore and truststore
> password configuration
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-4463
> URL: https://issues.apache.org/jira/browse/QPID-4463
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.21
> Reporter: Keith Wall
> Attachments: AbstractLDAPSSLSocketFactory.java
>
>
> To better support use cases where the Broker is required to authenticate
> against a Directory protected by SSL, the Java Broker should accept
> truststore and truststore password via configuration.
> Currently the user is required to pass the JVM system properties
> javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword (which are
> effectively globals).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
