must look like this: package com.mycompany.myapp class Permission { User user String permission static constraints = { permission unique: 'user' } } Register the class name along with e = 'com.mycompany.myapp.Permission' You can add other properties and methods, but the plugin expects that there is a one-to-many between your user and permission classes, that the user property property name is “user” (regardless of the actual class name), and the permission property name is “permission”. If you need more flexibility, or perhaps to create this as a many-to-many, you can replace the

......................................................................................... 21 PERMISSION .............................................................................................. shiro.realm.text.PropertiesRealm： user.username=password,role1,role2 指定用户 名/密码及其角色；role.role1=permission1,permission2 指定角色及权限信息； org.apache.shiro.realm.jdbc.JdbcRealm：通过 sql 查询相应的信息，如“select password from where username = ?”获取用户密码及盐；“select role_name from user_roles where username = ?” 获取用户角色；“select permission from roles_permissions where role_name = ?”获取角色对 应的权限信息；也可以调用相应的 api 进行自定义 sql； JDBC Realm

runtime. • MQTT interceptors. • Support adding/deleting queues via CLI. • New "browse" security permission for clients who only wish to look at messages. • Option to populate JMSXUserID. • "Dual authentication" <permission type="view" roles="admin"/> <permission type="edit" roles="admin"/> To grant the managerRole role view permission to just the activemq.management <permission type="view" roles="managerRole"/> To ensure no user has permission to force a failover using the broker (server control)

runtime. • MQTT interceptors. • Support adding/deleting queues via CLI. • New "browse" security permission for clients who only wish to look at messages. • Option to populate JMSXUserID. • "Dual authentication" <permission type="view" roles="admin"/> <permission type="edit" roles="admin"/> To grant the managerRole role view permission to just the activemq.management <permission type="view" roles="managerRole"/> To ensure no user has permission to force a failover using the broker (server control)

runtime. • MQTT interceptors. • Support adding/deleting queues via CLI. • New "browse" security permission for clients who only wish to look at messages. • Option to populate JMSXUserID. • "Dual authentication" <permission type="view" roles="admin"/> <permission type="edit" roles="admin"/> To grant the managerRole role view permission to just the activemq.management <permission type="view" roles="managerRole"/> To ensure no user has permission to force a failover using the broker (server control)

runtime. • MQTT interceptors. • Support adding/deleting queues via CLI. • New "browse" security permission for clients who only wish to look at messages. • Option to populate JMSXUserID. • "Dual authentication" <permission type="view" roles="admin"/> <permission type="edit" roles="admin"/> To grant the managerRole role view permission to just the activemq.management <permission type="view" roles="managerRole"/> To ensure no user has permission to force a failover using the broker (server control)

MQTT interceptors. Versions 18 Support adding/deleting queues via CLI. New "browse" security permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" Broker Connections 68 Important: The target endpoint needs permission for all operations that you configure. Therefore, If you are using a security manager, ensure and ‘*’. The <permission> sub-elements Each can have a list of <permission> elements, each of which defines a specific permission-roles mapping. Each permission has 2 attributes

at runtime. MQTT interceptors. Support adding/deleting queues via CLI. New "browse" security permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" Broker Connections 69 Important: The target endpoint needs permission for all operations that you configure. Therefore, If you are using a security manager, ensure and ‘*’. The <permission> sub-elements Each can have a list of <permission> elements, each of which defines a specific permission-roles mapping. Each permission has 2 attributes

at runtime. MQTT interceptors. Support adding/deleting queues via CLI. New "browse" security permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" startBrokerConnection(connectionName) is called on the ServerController. Important: The target endpoint needs permission for all operations that configured. Therefore, If a security manager is being used, ensure to ‘*’. The <permission> sub-elements Each can have a list of <permission> elements, each of which defines a specific permission- roles mapping. Each permission has 2 attributes

at runtime. MQTT interceptors. Support adding/deleting queues via CLI. New "browse" security permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" Broker Connections 79 Important: The target endpoint needs permission for all operations that are configured. Therefore, If a security manager is being used, ensure and ‘*’. The <permission> sub-elements Each can have a list of <permission> elements, each of which defines a specific permission-roles mapping. Each permission has 2 attributes