| Interface | Description |
|---|---|
| ActiveMQSecurityManager |
Use to validate whether a user has is valid to connect to the server and perform certain
functions
|
| ActiveMQSecurityManager2 |
Used to validate whether a user is authorized to connect to the
server and perform certain functions on certain destinations.
|
| ActiveMQSecurityManager3 |
Used to validate whether a user is authorized to connect to the
server and perform certain functions on certain destinations.
|
| ActiveMQSecurityManager4 |
Used to validate whether a user is authorized to connect to the
server and perform certain functions on certain addresses
This is an evolution of
ActiveMQSecurityManager3
that adds the ability to specify the JAAS domain per call. |
| ActiveMQSecurityManager5 |
Used to validate whether a user is authorized to connect to the
server and perform certain functions on certain addresses
This is an evolution of
ActiveMQSecurityManager4
that integrates with the new Subject caching functionality. |
| UserManagement |
| Class | Description |
|---|---|
| ActiveMQBasicSecurityManager |
All user and role state (both in memory and on disk) is maintained by the underlying StorageManager
|
| ActiveMQJAASSecurityManager |
This implementation delegates to the JAAS security interfaces.
|
| ActiveMQSecurityManagerImpl | Deprecated |
Copyright © 2025 JBoss by Red Hat. All rights reserved.