[jboss-jira] [JBoss JIRA] (WFCORE-1037) TrustManager algorithm of https ports can not be changed
Darran Lofthouse (JIRA)
issues at jboss.org
Sun Jan 8 10:15:00 EST 2017
[ https://issues.jboss.org/browse/WFCORE-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darran Lofthouse resolved WFCORE-1037.
--------------------------------------
Fix Version/s: 3.0.0.Alpha18
Resolution: Out of Date
The migration to WildFly Elytron allows full control of the TrustManager definition.
> TrustManager algorithm of https ports can not be changed
> --------------------------------------------------------
>
> Key: WFCORE-1037
> URL: https://issues.jboss.org/browse/WFCORE-1037
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 2.0.0.CR6
> Reporter: Arto Huusko
> Assignee: Darran Lofthouse
> Fix For: 3.0.0.Alpha18
>
>
> The trust manager algorithm used by undertow can not be changed. The server configuration file does not contain any support for changing the algorithm, nor is Java standard system property ssl.TrustManagerFactory.algorithm honored. Apparently undertow forces use of PKIX.
> In earlier jboss versions jboss-web supported changing trust manager algorithm in the Connector element in the web server configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list