[
https://issues.jboss.org/browse/AS7-5694?page=com.atlassian.jira.plugin.s...
]
xiang yingbing commented on AS7-5694:
-------------------------------------
It is NOT a bug.
Sorry!
I found the solution:
https://docs.jboss.org/author/display/AS71/Messaging+configuration
Security Domain for Users
By default, HornetQ will use the "other" JAAS security domain. This domain is
used to authenticate users making connections to HornetQ and then they are authorized to
perform specific functions based on their role(s) and the security-settings described
above. This domain can be changed by using security-domain, e.g.:
<subsystem xmlns="urn:jboss:domain:messaging:1.0">
[...]
<security-domain>mySecurityDomain</security-domain>
[...]
</subsystem>
Correct usage is:
<subsystem xmlns="urn:jboss:domain:messaging:1.3">
<hornetq-server>
<persistence-enabled>true</persistence-enabled>
<journal-file-size>102400</journal-file-size>
<journal-min-files>2</journal-min-files>
<security-domain>nms-jaas-security-domain</security-domain>
...
Messaging subsystem should support JAAS
---------------------------------------
Key: AS7-5694
URL:
https://issues.jboss.org/browse/AS7-5694
Project: Application Server 7
Issue Type: Feature Request
Components: JMS
Affects Versions: 7.1.1.Final
Reporter: xiang yingbing
Assignee: Jeff Mesnil
Labels: JAAS, Messaging
Original Estimate: 1 week
Remaining Estimate: 1 week
<subsystem xmlns="urn:jboss:domain:messaging:1.3"> should support JAAS.
currently, <subsystem
xmlns="urn:jboss:domain:messaging:1.3">.<security-settings>.<security-setting
match="#">. <permission type="send" roles="admin,
guest"/>
suppport JAAS.Authentication, but does NOT support JAAS.Authorization.
Please refer to the discussion:
https://community.jboss.org/message/763483#763483
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira