HornetQ Security Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
:[[WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Security|HornetQ Security Concepts]] | :[[WildFly_HornetQ-Based_Messaging_Subsystem_Concepts#Security|HornetQ Security Concepts]] | ||
</blockquote> | </blockquote> | ||
This behavior can be disabled in configuration. For details see [[#Disabling_Security|Disabling Security]] below. | |||
=Disabling Security= | =Disabling Security= | ||
By default, HornetQ requires a username and a password to be specified when creating a connection. This behavior can be disabled, and anonymous connections can be created, by turning "security-enabled" to false: | |||
<pre> | <pre> | ||
Latest revision as of 16:58, 3 April 2017
Internal
Overview
By default, security is enabled and ConnectionFactories must specify a username and a password to establish connections. For more on security concepts, see:
This behavior can be disabled in configuration. For details see Disabling Security below.
Disabling Security
By default, HornetQ requires a username and a password to be specified when creating a connection. This behavior can be disabled, and anonymous connections can be created, by turning "security-enabled" to false:
<subsystem xmlns="urn:jboss:domain:messaging:1.4">
<hornetq-server>
...
<security-enabled>false</security-enabled>
...
</hornetq-server>
</subsystem>