You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (Commented) (JIRA)" <ji...@apache.org> on 2012/03/27 11:59:26 UTC

[jira] [Commented] (CXF-4204) CXF https transport should support to specify the cert alias name

    [ https://issues.apache.org/jira/browse/CXF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239356#comment-13239356 ] 

Freeman Fang commented on CXF-4204:
-----------------------------------

commit fix
http://svn.apache.org/viewvc?rev=1305775&view=rev on trunk
http://svn.apache.org/viewvc?rev=1305786&view=rev on 2.5.x branch
http://svn.apache.org/viewvc?rev=1305789&view=rev on 2.4.x branch

                
> CXF https transport should support to specify the cert alias name
> -----------------------------------------------------------------
>
>                 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 and client 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