You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org> on 2012/03/02 23:35:59 UTC
[jira] [Closed] (AMQ-2288) AdvisoryBroker does not set up
SecurityContext so advisory message not sent on startup
[ https://issues.apache.org/jira/browse/AMQ-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-2288.
-----------------------------
Resolution: Duplicate
This was fixed by AMQ-1704
> AdvisoryBroker does not set up SecurityContext so advisory message not sent on startup
> --------------------------------------------------------------------------------------
>
> Key: AMQ-2288
> URL: https://issues.apache.org/jira/browse/AMQ-2288
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.2.0
> Reporter: Dave Syer
> Priority: Minor
> Fix For: 5.x
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> AdvisoryBroker does not set up SecurityContext so advisory message not sent on startup. The AdvisoryBroker has a nowMasterBroker() method that sends an advisory message without a SecurityContext. If the authorization plugin is being used, then it fails because the user is not authenticated. It looks to me like the fix would be to add a line to that method:
> {code}
> context.setSecurityContext(SecurityContext.BROKER_SECURITY_CONTEXT);
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira