You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org> on 2010/03/13 04:45:27 UTC
[jira] Created: (QPID-2446) JMS Client should allow a trust/key
store per connection rather than one per JVM
JMS Client should allow a trust/key store per connection rather than one per JVM
--------------------------------------------------------------------------------
Key: QPID-2446
URL: https://issues.apache.org/jira/browse/QPID-2446
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.6
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Fix For: 0.7
The JMS client needs to extract the user ID from the external mechanism when SASL EXTERNAL is used.
Ex. If we use SSL as the external mechanism, we need to create an user ID based on the client certificate.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-2446) JMS Client should allow a trust/key
store per connection rather than one per JVM
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu resolved QPID-2446.
------------------------------------
Resolution: Fixed
"testCreateSSLContextFromConnectionURLParams" in SSLTest covers this case.
> JMS Client should allow a trust/key store per connection rather than one per JVM
> --------------------------------------------------------------------------------
>
> Key: QPID-2446
> URL: https://issues.apache.org/jira/browse/QPID-2446
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.6
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
>
> In some cases you would need to create connections with multiple SSL certificates from the same JVM.
> One such option is to have each certificate in it's own keystore (and truststore if necessary).
> Another option is to have multiple certificates in the same keystore - QPID-2447.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2446) JMS Client should allow a trust/key
store per connection rather than one per JVM
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-2446:
-----------------------------------
Description:
In some cases you would need to create connections with multiple SSL certificates from the same JVM.
One such option is to have each certificate in it's own keystore (and truststore if necessary).
Another option is to have multiple certificates in the same keystore.
was:
The JMS client needs to extract the user ID from the external mechanism when SASL EXTERNAL is used.
Ex. If we use SSL as the external mechanism, we need to create an user ID based on the client certificate.
> JMS Client should allow a trust/key store per connection rather than one per JVM
> --------------------------------------------------------------------------------
>
> Key: QPID-2446
> URL: https://issues.apache.org/jira/browse/QPID-2446
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.6
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
>
> In some cases you would need to create connections with multiple SSL certificates from the same JVM.
> One such option is to have each certificate in it's own keystore (and truststore if necessary).
> Another option is to have multiple certificates in the same keystore.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2446) JMS Client should allow a trust/key
store per connection rather than one per JVM
Posted by "Rajith Attapattu (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajith Attapattu updated QPID-2446:
-----------------------------------
Description:
In some cases you would need to create connections with multiple SSL certificates from the same JVM.
One such option is to have each certificate in it's own keystore (and truststore if necessary).
Another option is to have multiple certificates in the same keystore - QPID-2447.
was:
In some cases you would need to create connections with multiple SSL certificates from the same JVM.
One such option is to have each certificate in it's own keystore (and truststore if necessary).
Another option is to have multiple certificates in the same keystore.
Issue Type: Improvement (was: Bug)
> JMS Client should allow a trust/key store per connection rather than one per JVM
> --------------------------------------------------------------------------------
>
> Key: QPID-2446
> URL: https://issues.apache.org/jira/browse/QPID-2446
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: 0.6
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.7
>
>
> In some cases you would need to create connections with multiple SSL certificates from the same JVM.
> One such option is to have each certificate in it's own keystore (and truststore if necessary).
> Another option is to have multiple certificates in the same keystore - QPID-2447.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org