You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Shawn McKinney (JIRA)" <ji...@apache.org> on 2016/01/28 15:22:39 UTC
[jira] [Commented] (FC-143) Let LdapClientTrustStoreManager read
trust store from jar
[ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121552#comment-15121552 ]
Shawn McKinney commented on FC-143:
-----------------------------------
I think this is a good idea.
> Let LdapClientTrustStoreManager read trust store from jar
> ---------------------------------------------------------
>
> Key: FC-143
> URL: https://issues.apache.org/jira/browse/FC-143
> Project: FORTRESS
> Issue Type: Improvement
> Affects Versions: 1.0.0-RC41
> Reporter: Jan Sindberg
> Priority: Minor
> Attachments: [FC-143]_-_Let_LdapClientTrustStoreManager_read_trust_store_from_jar.patch
>
>
> *Use case *
> Creating a small utility to initialize configuration (setting system properties) which serves up the right parameters and also contains trust stores.
> That way we can quickly set up for test locally at developer machines, as well on test environments and prod.
> *Problem*
> LdapClientTrustStoreManager expects a fully-qualified name of a Java TrustStore on local file system.
> *Proposed solution*
> Get an input stream to the trust store. Test if it is a local file. If it is not, then test if an inputstream can be created from resources.
> Patch attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)