You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Howard Gao (JIRA)" <ji...@apache.org> on 2017/04/25 01:20:04 UTC
[jira] [Resolved] (ARTEMIS-1122) ActiveMQJAASSecurityManager class
loading issue
[ https://issues.apache.org/jira/browse/ARTEMIS-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard Gao resolved ARTEMIS-1122.
---------------------------------
Resolution: Fixed
> ActiveMQJAASSecurityManager class loading issue
> -----------------------------------------------
>
> Key: ARTEMIS-1122
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1122
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.0.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 2.next
>
>
> The ActiveMQJAASSecurityManager class uses LoginContext to validate users and roles. LoginContext loads LoginModule classes defined in the configuration (login.config) using current thread's context classloader.
> Normally this wouldn't be a problem but when a caller thread comes from JMX (for example a client calls QueueControl.sendMessage() via JMX) the caller thread has a different context class loader. This will cause the LoginContext fails to load the LoginModule class (e.g. org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule) and the validation will fail even correct credentials are supplied.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)