activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r992651 - in /websites/production/activemq/content: cache/main.pageCache security.html
Date Wed, 13 Jul 2016 06:22:43 GMT
Author: buildbot
Date: Wed Jul 13 06:22:43 2016
New Revision: 992651

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/security.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/security.html
==============================================================================
--- websites/production/activemq/content/security.html (original)
+++ websites/production/activemq/content/security.html Wed Jul 13 06:22:43 2016
@@ -414,7 +414,7 @@ objectClass: top
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">activemq.username=system
 activemq.password=manager
 </pre>
-</div></div><h4 id="Security-EncryptedPasswords">Encrypted Passwords</h4><p>As
of version 5.4.1 you can also use <a shape="rect" href="encrypted-passwords.html">Encrypted
passwords</a> with your broker</p><h3 id="Security-MessagelevelAuthorization">Message
level Authorization</h3><p>It's also possible to authorize each single message
using some content based authorization policy of your choosing. In comparison to the other
security options described before, Message level Authorization requires a bit more than just
some configuration. You have to start with creating a new maven project and add the&#160;<a
shape="rect" class="external-link" href="https://mvnrepository.com/artifact/org.apache.activemq/activemq-all"
rel="nofollow">activemq-all</a> maven dependency (in the same version as your activemq
installation) to the pom.xml of your new project.<br clear="none">In the next step you
have to create a new Java class and let it implement the org.apache.activemq.security.MessageAuthoriz
 ationPolicy interface. After that, simply add a method with signature:</p><p>public
boolean isAllowedToConsume(ConnectionContext context, Message message){...}</p><p>to
the new Java class. For usage of tis Message level Authorization policy, the Java class has
to be packaged as jar and added to the /lib folder of ActiveMQ. In the last step, the policy
has to be configured on the broker directly by using the * messageAuthorizationPolicy* property
or add it to the XML as follows</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+</div></div><h4 id="Security-EncryptedPasswords">Encrypted Passwords</h4><p>As
of version 5.4.1 you can also use <a shape="rect" href="encrypted-passwords.html">Encrypted
passwords</a> with your broker</p><h3 id="Security-MessagelevelAuthorization">Message
level Authorization</h3><p>It's also possible to authorize each single message
using some content based authorization policy of your choosing. In comparison to the other
security options described before, Message level Authorization requires a bit more than just
some configuration. You have to start with creating a new maven project and add the&#160;<a
shape="rect" class="external-link" href="https://mvnrepository.com/artifact/org.apache.activemq/activemq-all"
rel="nofollow">activemq-all</a> maven dependency (in the same version as your activemq
installation) to the pom.xml of your new project.<br clear="none">In the next step you
have to create a new Java class and let it implement the org.apache.activemq.security.MessageAuthoriz
 ationPolicy interface. After that, simply add a method with signature:</p><p>public
boolean isAllowedToConsume(ConnectionContext context, Message message){...}</p><p>to
the new Java class. For usage of your own Message level Authorization policy, the Java class
has to be packaged as jar and added to the /lib folder of ActiveMQ to make it available for
ActiveMQ. In the last step, it has to be configured on the broker directly by using the *
messageAuthorizationPolicy* property or add it to the XML as follows</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">&lt;broker&gt;
   ..
   &lt;messageAuthorizationPolicy&gt;



Mime
View raw message