activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sepand Mavandadi (JIRA)" <>
Subject [jira] Updated: (AMQ-912) ActiveMQ support for SSL authentication and authorization
Date Fri, 08 Sep 2006 21:52:23 GMT
     [ ]

Sepand Mavandadi updated AMQ-912:

    Attachment: svn_diff.txt

This is an update to the patch. It fixes some minor problems encountered when using a newer
revision as base.

> ActiveMQ support for SSL authentication and authorization
> ---------------------------------------------------------
>                 Key: AMQ-912
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport, Test Cases
>            Reporter: Sepand Mavandadi
>         Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.txt
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
> This patch adds new Transports, Brokers, and Plugins needed for authentication and authorization
based on SSL certificates.
> It also adds a few unit tests for the mentioned classes.
> The new (or heavily modified) SslTransport, SslTransportServer, and SslTransportFactory
classes allow for access to the underlying socket's need and want client auth settings. If
a certificate is found, it is set as the transportContext of the created connection.
> The JaasCertificateAuthenticationBroker uses the new CertificateLoginModule to authenticate
certificates (this class is abstract to allow for different backends for certificate authentication,
a concrete class is TextFileCertificateLoginModule).
> JaasCertificateAuthenticationBroker also sets the security context's user name to that
provided for the certificate by the login module. This allows for authorization using the
existing authorization broker.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message