[
https://jira.jboss.org/jira/browse/JBAS-5814?page=com.atlassian.jira.plug...
]
Stefan Guilhen closed JBAS-5814.
--------------------------------
Resolution: Done
JBossASSecurityMetadataStore is now configured as a mc bean in metadata-jboss-beans.xml
and gets a reference to the SecurityManagement implementation through injection. The JMX
annotation has also been added to the configuration to export the management view of the
bean to the jmx-console.
The messaging application-policy was also moved from login-config.xml to
metadata-jboss-beans.xml, next to the bean that uses it (JBossASSecurityMetadataStore).
Move jboss.messaging:service=SecurityStore to
messaging-jboss-beans.xml
-----------------------------------------------------------------------
Key: JBAS-5814
URL:
https://jira.jboss.org/jira/browse/JBAS-5814
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JMS (JBoss Messaging)
Affects Versions: JBossAS-5.0.0.CR1
Reporter: Stefan Guilhen
Assignee: Stefan Guilhen
Fix For: JBossAS-5.0.0.CR2
Anil has suggested that we make the JBossAsSecurityMetadataStore a regular mc bean and
inject the security management implementation that is used by this component to
authenticate and authorize users. This basically involves moving the bean from
messaging-service.xml to messaging-jboss-beans.xml, injecting the sec management and
inserting the JMX annotation to export the management view of this bean to the jmx
console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira