[
https://issues.apache.org/jira/browse/KNOX-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168989#comment-17168989
]
ASF subversion and git services commented on KNOX-2434:
-------------------------------------------------------
Commit 808410042a960b936a8d85cb658b2cad18ed60db in knox's branch
refs/heads/master from Kevin Risden
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=8084100 ]
KNOX-2434 - Knox should fallback to JDK default keystore/truststore type
instead of hardcoding JKS (#366)
Signed-off-by: Kevin Risden <kris...@apache.org>
> Knox should fallback to JDK default keystore/truststore type instead of
> hardcoding JKS
> --------------------------------------------------------------------------------------
>
> Key: KNOX-2434
> URL: https://issues.apache.org/jira/browse/KNOX-2434
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 1.4.0
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Major
> Fix For: 1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently Knox has a few configuration options for overriding the
> keystore/truststore type and if these are not specified it falls back to
> hardcoded "JKS". This should fallback instead of the JDK default configured
> keystore/truststore type. This will cause issues when an administrator wants
> to control the keystore type globally at the JDK level. This happens when
> doing FIPS crypto modules.
> It would be better to use KeyStore.getDefaultType() instead of hardcoding JKS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
