public interface ActiveMQSecurityManager5 extends ActiveMQSecurityManager
ActiveMQSecurityManager4
that integrates with the new Subject caching functionality.| Modifier and Type | Method and Description |
|---|---|
Subject |
authenticate(String user,
String password,
RemotingConnection remotingConnection,
String securityDomain)
is this a valid user.
|
boolean |
authorize(Subject subject,
Set<Role> roles,
CheckType checkType,
String address)
Determine whether the given user has the correct role for the given check type.
|
getDomain, init, validateUser, validateUserAndRoleSubject authenticate(String user, String password, RemotingConnection remotingConnection, String securityDomain)
ActiveMQSecurityManager.validateUser(String, String).user - the userpassword - the user's passwordremotingConnection - the user's connection which contains any corresponding SSL certssecurityDomain - the name of the JAAS security domain to use (can be null)boolean authorize(Subject subject, Set<Role> roles, CheckType checkType, String address)
ActiveMQSecurityManager.validateUserAndRole(String, String, Set, CheckType).subject - the Subject to authorizeroles - the roles configured in the security-settingscheckType - which permission to validateaddress - the address (or FQQN) to grant access toCopyright © 2021 JBoss by Red Hat. All rights reserved.