Show Table of Contents
29.6. HornetQ Security Manager
The HornetQ security manager provides tight integration with the JBoss Enterprise Application Platform security model.
The class name of this security manager is
org.hornetq.integration.jboss.security.JBossASSecurityManager
An example of how the
JBossASSecurityManager is configured is described in <JBOSS_HOME>/jboss-as/server/<PROFILE>/deploy/hornetq/hornetq-jboss-beans.xml.
29.6.1. Configuring Client Login
JBoss Enterprise Application Platform can be configured to allow client login. This is when a Java EE component such as a Servlet or EJB sets security credentials on the current security context, and these are used throughout the call.
HornetQ can use these settings when sending or consuming messages by changing the allowClientLogin property to
true (default is false) in <JBOSS_HOME>/jboss-as/server/<PROFILE>/deploy/hornetq/hornetq-jboss-beans.xml file. This bypasses HornetQ authentication, and propagates the provided Security Context.
If HornetQ should authenticate using the propagated security, set the
authoriseOnClientLogin to true in addition to allowClientLogin.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.