To the groups.properties..
* AMQ-users=client1,client2
* AMQ-users=“client1”,”client2”
*AMW-users=‘client1’,’client2'


I want my authorization to read these 2 clients and create 2 topic destination 
on web console. But nothing worked out. Any help?

Thanks!

Best regards,
Crishel Yumul
DevOps
TORO Limited

> On Aug 1, 2016, at 3:34 PM, Hassen Bennour [via ActiveMQ] 
> <ml-node+s2283324n4714897...@n4.nabble.com> wrote:
> 
> Hello, 
> where you done this ?*. I've tried adding (" ") and (' '), but it didn't 
> worked out. * 
> 
> You can do this by adding an authorizationEntry for each user. 
> 
> <authorizationPlugin> 
>         <map> 
>           <authorizationMap> 
>             <authorizationEntries> 
>               <authorizationEntry topic="client1.some.topic.>" read="client1" 
> write="client1" admin="AMQ-admin,client1" /> 
>               <authorizationEntry topic="client2.some.topic.>" read="client2" 
> write="client2" admin="AMQ-admin,client2" /> 
>             </authorizationEntries> 
>           </authorizationMap> 
>         </map> 
> </authorizationPlugin> 
> 
> 
> 
> Kind regards. 
> 
> *BENNOUR HASSEN* 
> 
> *SOA **Architect **/ **Java **Software Engineer* 
> 
> 2016-08-01 3:11 GMT+02:00 crishel.yumul <[hidden email] 
> <x-msg://2/user/SendEmail.jtp?type=node&node=4714897&i=0>>: 
> 
> > Thank you, Hassen! :) 
> > I've already configured the jaasAuth plugin... 
> > 
> > Here's my follow-up question: 
> > In the group.properties, I have 2 users. Client1 and Client 2. Both are 
> > configured to have own topic ("client1.some.topic" and 
> > "client2.some.topic"). But upon running my broker, my broker console only 
> > shows the client2.some.topic.. I've tried adding (" ") and (' '), but it 
> > didn't worked out. 
> > 
> > Now, is there any way I can command my broker to authorize the 2 users with 
> > their own topic name? So that the web console can display both their topic? 
> > 
> > Thank you! Hope there will be an answer. It will be greatly appreciated! 
> > 
> > 
> > Regards, 
> > Crishel Yumul 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://activemq.2283324.n4.nabble.com/For-each-user-group-properties-tp4714741p4714892.html
> >  
> > <http://activemq.2283324.n4.nabble.com/For-each-user-group-properties-tp4714741p4714892.html>
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com 
> > <http://nabble.com/>. 
> > 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://activemq.2283324.n4.nabble.com/For-each-user-group-properties-tp4714741p4714897.html
>  
> <http://activemq.2283324.n4.nabble.com/For-each-user-group-properties-tp4714741p4714897.html>
> To unsubscribe from For each user group.properties, click here 
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4714741&code=Y3Jpc2hlbC55dW11bEB0b3JvLmlvfDQ3MTQ3NDF8LTE2NTIyNjIwNjQ=>.
> NAML 
> <http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/For-each-user-group-properties-tp4714741p4714898.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to