activemq-dev mailing list archives

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

Great to see you liked it =)
One thing I've noticed, I moved 

The latest revision has both files in there (the patch file doesn't show the move).

If you agree with the change (we already talked on the mailing list), please remove the copy
in the core module. If you don't, you can just remove the one under the jaas module and change
the references I've made to it (it should be easy, there aren't too many).

> 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
>             Fix For: 4.1
>         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