分指 定角色即权限信息； org.apache.shiro.realm.text.PropertiesRealm： user.username=password,role1,role2 指定用户 名/密码及其角色；role.role1=permission1,permission2 指定角色及权限信息； org.apache.shiro.realm.jdbc.JdbcRealm：通过 sql 查询相应的信息，如“select from users where username = ?”获取用户密码及盐；“select role_name from user_roles where username = ?” 获取用户角色；“select permission from roles_permissions where role_name = ?”获取角色对 应的权限信息；也可以调用相应的 api 进行自定义 sql； 本文将使用 mysql 数据库及 druid 连接池； 2、到数据库 shiro 下建三张表：users（用户名/密码）、user_roles（用户/角色）、roles_permissions （角色/权限），具体请参照 shiro-example-chapter2/sql/shiro.sql；并添加一个用户记录，用 户名/密码为 zhang/123； 3、ini 配置（shiro-jdbc-realm

zabbix 用户。在提示下请输入密码并再次确认密码。（注意，可能首 先要求输入 sudo 命令对应的用户密码）： You need to have database user with permissions to create database objects. The following shell command will create user zabbix. Specify password UTF8 字符集。检查当前设置： We assume that a zabbix database user with password password exists and has permissions to create database objects in ORCL service located on the host Oracle database server with a user HISTORY 5; mysql> CREATE ROLE 'zbx_srv_role', 'zbx_web_role'; mysql> GRANT SELECT, UPDATE, DELETE, INSERT, CREATE, DROP, ALTER, INDEX, REFERENCES ON zabbix.* TO 'zbx_srv_role'; mysql> GRANT SELECT, UPDATE

Architecture 架构 4. Configuration 配置 II. Core 核心 5. Authentication 认证 6. Authorization 授权 6.1. Permissions 权限 7. Realms 8. Session Management 9. Cryptography 密码 III. Web Applications 10. Web 10.1 ------------------------ # Users and their (optional) assigned roles # username = password, role1, role2, ..., roleN # ----------------------------------------------------------------------------- ----------------------------------------------------------------------------- # Roles with assigned permissions # roleName = perm1, perm2, ..., permN # ----------------------------------------------------

Alternatively you can use the search field to find a specific string or term. 建议 注解 Actual permissions might vary depending on your Weblate configuration. Anonymous users can only (if permitted) forward “Import as string needing edit”, or “Import as translated”. Overriding authorship With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the 注解 The proxy configuration needs to be done under user running Weblate (see also Filesystem permissions) and with HOME=$DATA_DIR/home (see DATA_DIR), otherwise Git executed by Weblate will not use it

Alternatively you can use the search field to find a specific string or term. 1.3.3 建议 注解: Actual permissions might vary depending on your Weblate configuration. Anonymous users can only (if permitted) forward “Import as string needing edit”, or “Import as translated”. Overriding authorship With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the 注解: The proxy configuration needs to be done under user running Weblate (see also Filesystem permissions) and with HOME=$DATA_DIR/home (see DATA_DIR), otherwise Git executed by Weblate will not use it

Alternatively you can use the search field to find a specific string or term. 1.3.3 建议 注解: Actual permissions might vary depending on your Weblate configuration. Anonymous users can only (if permitted) forward “Import as string needing edit”, or “Import as translated”. Overriding authorship With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the 注解: The proxy configuration needs to be done under user running Weblate (see also Filesystem permissions) and with HOME=$DATA_DIR/home (see DATA_DIR), otherwise Git executed by Weblate will not use it

Alternatively you can use the search field to find a specific string or term. 1.3.3 建议 注解: Actual permissions might vary depending on your Weblate configuration. Anonymous users can only (if permitted) forward “Import as string needing edit”, or “Import as translated”. Overriding authorship With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the 注解: The proxy configuration needs to be done under user running Weblate (see also Filesystem permissions) and with HOME=$DATA_DIR/home (see DATA_DIR), otherwise Git executed by Weblate will not use it

Alternatively you can use the search field to find a specific string or term. 建议 注解 Actual permissions might vary depending on your Weblate configuration. Anonymous users can only (if permitted) forward “Import as string needing edit”, or “Import as translated”. Overriding authorship With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the 注解 The proxy configuration needs to be done under user running Weblate (see also Filesystem permissions) and with HOME=$DATA_DIR/home (see DATA_DIR), otherwise Git executed by Weblate will not use it

Alternatively you can use the search field to find a specific string or term. 建议 注解 Actual permissions might vary depending on your Weblate configuration. Anonymous users can only (if permitted) forward “Import as string needing edit”, or “Import as translated”. Overriding authorship With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the 注解 The proxy configuration needs to be done under user running Weblate (see also Filesystem permissions) and with HOME=$DATA_DIR/home (see DATA_DIR), otherwise Git executed by Weblate will not use it

or term. 1.3. Translating using Weblate 11 The Weblate Manual, 发布 4.5.3 1.3.3 建议 注解: Actual permissions might vary depending on your Weblate configuration. Anonymous users can only (by default) forward “Import as string needing edit”, or “Import as translated”. Overriding authorship With admin permissions, you can also specify authorship of uploaded file. This can be useful in case you’ve received the (int) –群组的 ID POST /api/groups/(int: id)/roles/ 将角色与群组关联。 参数 • id (int) –群组的 ID 表格参数 • string role_id –唯一的角色 ID 1.12. Weblate 的 REST API 89 The Weblate Manual, 发布 4.5.3 POST /api/groups/(int: id)/components/