Search

29.6. HornetQ Security Manager

download PDF
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.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.