activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <>
Subject [jira] Commented: (AMQ-912) ActiveMQ support for SSL authentication and authorization
Date Mon, 18 Sep 2006 21:00:23 GMT
    [ ] 
Hiram Chirino commented on AMQ-912:

Hi Kelly,

Yep I got the same results with xbean.  The error was not too friendly to figure out what
was going wrong so I opened and resolved issue:

The reason xbean was barfing is that the patch produced a .java file that was empty.  The
current version of xbean could not cope with that, but I've applied a fix to it so it should
not be a problem with future versions.

Looking into the patch now.

> ActiveMQ support for SSL authentication and authorization
> ---------------------------------------------------------
>                 Key: AMQ-912
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport, Test Cases
>            Reporter: Sepand Mavandadi
>         Assigned To: Hiram Chirino
>         Attachments: ssl_certifiacte_auth_patch.txt, svn_diff.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