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 (Created) (JIRA)" <ji...@apache.org> on 2012/03/26 13:14:27 UTC
[jira] [Created] (CXF-4204) CXF http-jetty transport should support
to specify the cert alias name when use https
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
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
[jira] [Updated] (CXF-4204) CXF https transport should support to
specify the cert alias name
Posted by "Freeman Fang (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated CXF-4204:
------------------------------
Description:
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.
was:
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.
Summary: CXF https transport should support to specify the cert alias name (was: CXF http-jetty transport should support to specify the cert alias name when use https)
> 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
[jira] [Commented] (CXF-4204) CXF https transport should support to
specify the cert alias name
Posted by "Freeman Fang (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (CXF-4204) CXF https transport should support to
specify the cert alias name
Posted by "Freeman Fang (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved CXF-4204.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.6
2.5.3
2.4.7
> 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
> Fix For: 2.4.7, 2.5.3, 2.6
>
>
> 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
[jira] [Commented] (CXF-4204) CXF https transport should support to
specify the cert alias name
Posted by "Freeman Fang (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239357#comment-13239357 ]
Freeman Fang commented on CXF-4204:
-----------------------------------
I still need change new added HTTPJettyTransportActivator on trunk to set certAlias
> 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
[jira] [Assigned] (CXF-4204) CXF http-jetty transport should
support to specify the cert alias name when use https
Posted by "Freeman Fang (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned CXF-4204:
---------------------------------
Assignee: Freeman Fang
> 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
[jira] [Commented] (CXF-4204) CXF http-jetty transport should
support to specify the cert alias name when use https
Posted by "Freeman Fang (Commented) (JIRA)" <ji...@apache.org>.
[ 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