activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-330) Support using a different Authorizer Authenticator implementations.
Date Sat, 13 Jul 2013 18:19:48 GMT

    [ https://issues.apache.org/jira/browse/APLO-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707807#comment-13707807
] 

Hiram Chirino commented on APLO-330:
------------------------------------

Ok we now support changing the Authorizer and Authenticator implementation class used by broker.
 

Firstly you need to implement the SecurityFactory trait.  For example:

https://github.com/apache/activemq-apollo/blob/trunk/apollo-stomp/src/test/scala/org/apache/activemq/apollo/stomp/test/UserOwnershipSecurityFactory.scala#L29

Then you need to set the 'security_factory' attribute of the broker element to the name of
the class you implemented it with.  For example:
https://github.com/apache/activemq-apollo/blob/trunk/apollo-stomp/src/test/resources/apollo-stomp-custom-security.xml#L18


                
> Support using a different Authorizer Authenticator implementations.
> -------------------------------------------------------------------
>
>                 Key: APLO-330
>                 URL: https://issues.apache.org/jira/browse/APLO-330
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-broker, apollo-dto
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 1.7
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message