[
https://issues.apache.org/jira/browse/CXF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239220#comment-13239220
]
Freeman Fang commented on CXF-4204:
-----------------------------------
actually it's same case on the client side when configure http:conduit, both
client and server side https transport should support to specify the cert alias
> CXF http-jetty transport should support to specify the cert alias name when
> use https
> -------------------------------------------------------------------------------------
>
> Key: CXF-4204
> URL: https://issues.apache.org/jira/browse/CXF-4204
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Freeman Fang
> Assignee: Freeman Fang
>
> when use https, the server side key store may have multiple private keys and
> certificates, but currently in CXF there's no way to specify which cert
> should be used, so if customer keystore has multiple certificates, which one
> is picked up become uncertain
> Jetty SslContextFactory already provide api
> {code}
> public void setCertAlias(String certAlias)
> {code}
> since Jetty 7.3.1, CXF should be able to expose this configuration as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
