I have a similar request to : http://activemq.2283324.n4.nabble.com/Is-it-possible-to-use-Client-Certs-for-Authentication-Authorization-for-Apollo-tt4668985.html#a4669234
Is there a way to authorize dynamic destinations with Apache Apollo MQ? What I would like is to make it so that 1) users may write only to a shared topic but restrict read to an server/admin. This topic is to send messages to a server. 2) Users may read from their own private topic but no one but the server/admin may write to it. For Example: Topic User rights Server/Admin rights /public Write only Read only /user/foo ONLY the user foo may read Write only /user/bar ONLY the user bar may read Write only /user/<username> ONLY the <username> may read Write only Now for the interesting part. This must work with dynamic topics. The user's name is NOT known ahead of time. I had this working with Apache ActiveMQ using a custom security_factory but am not sure how to do with with Apollo. Based on the above post is looks like I need to write some sort of plugin but I only know Java not scala. <broker xmlns="http://activemq.apache.org/schema/activemq/apollo"; security_factory="org.apache.activemq.apollo.stomp.test.UserOwnershipSecurityFactory"> Thanks for any help. -- View this message in context: http://activemq.2283324.n4.nabble.com/Is-there-a-way-to-authorize-dynamic-destinations-with-Apache-Apollo-MQ-tp4694359.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
