directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn McKinney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FC-143) Let LdapClientTrustStoreManager read trust store from jar
Date Fri, 29 Jan 2016 15:23:39 GMT

    [ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123584#comment-15123584
] 

Shawn McKinney commented on FC-143:
-----------------------------------

Jan, here is what I think needs to be done here:

1. remove the pushbackstream (not needed here)
2. leave code to find on classpath
3. readd code to choose file from fully qualified path.

WDYT?

> 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
>             Fix For: 1.0.0-RC41
>
>         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)

Mime
View raw message