[jboss-jira] [JBoss JIRA] (WFLY-5259) truststore path is ignored if provider is not JKS
Thomas Diesler (JIRA)
issues at jboss.org
Wed Sep 2 06:05:05 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler updated WFLY-5259:
---------------------------------
Component/s: (was: ConfigAdmin)
> truststore path is ignored if provider is not JKS
> -------------------------------------------------
>
> Key: WFLY-5259
> URL: https://issues.jboss.org/browse/WFLY-5259
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 9.0.1.Final
> Reporter: Arto Huusko
> Assignee: Thomas Diesler
>
> truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS.
> This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working.
> We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured.
> Even standard java supports PKCS12 truststores, where the same problem would occur.
> So I would suggest that
> - if provider is JKS, path is mandatory
> - if provider is not JKS, but path is specified, it is passed to the provider
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list