[
https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn McKinney resolved FC-143.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0-RC41
Applied the patch. Had to correct a minor error where this code:
if (url.getProtocol().equals("file"))
{
final File file = new File(trustStoreFile);
didn't work because it was using the file name instead of url. Changed to this:
if (url.getProtocol().equals("file"))
{
final File file = new File(url.getFile());
and it worked as expected, trust store now found on classpath.
> 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)
