[jboss-jira] [JBoss JIRA] (WFLY-7472) Elytron key/trust-manager-factory default algorithm
Martin Choma (JIRA)
issues at jboss.org
Fri Nov 4 03:53:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Choma moved JBEAP-6882 to WFLY-7472:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7472 (was: JBEAP-6882)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
(was: User Experience)
Affects Version/s: 11.0.0.Alpha1
(was: 7.1.0.DR7)
> Elytron key/trust-manager-factory default algorithm
> ---------------------------------------------------
>
> Key: WFLY-7472
> URL: https://issues.jboss.org/browse/WFLY-7472
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Labels: user_experience
>
> {{key-manager-factory}} and {{trust-manager-factory}} requires user to specify algorithm.
> Consider defaulting in elytron code to {{TrustManagerFactory.getDefaultAlgorithm()}} and {{KeyManagerFactory.getDefaultAlgorithm()}}.
> It is java portable as for oracle java it returns SunX509 and for Ibm java IbmX509.
> This JIRA is in scope of "user experience", minimizing necessary user input configuration.
> David: "The trust manager definitely should use the default algorithm when none is given; in this case the algorithm name isn't an "algorithm" per se, it's just an implementation name."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list