本地英文版地址: ../en/security-trb-roles.html
Authorization exceptionsedit
Symptoms:
- I configured the appropriate roles and the users, but I still get an authorization exception.
- I can authenticate to LDAP, but I still get an authorization exception.
Resolution:
-
Verify that the role names associated with the users match the roles defined in the
roles.ymlfile. You can use theelasticsearch-userstool to list all the users. Any unknown roles are marked with*.bin/elasticsearch-users list rdeniro : admin alpacino : power_user jacknich : monitoring,unknown_role*
For more information about this command, see the
elasticsearch-userscommand. -
If you are authenticating to LDAP, a number of configuration options can cause this error.
group identification
Groups are located by either an LDAP search or by the "memberOf" attribute on the user. Also, If subtree search is turned off, it will search only one level deep. For all the options, see LDAP realm settings. There are many options here and sticking to the defaults will not work for all scenarios.
group to role mapping
Either the
role_mapping.ymlfile or the location for this file could be misconfigured. For more information, see Security files.role definition
The role definition might be missing or invalid.
To help track down these possibilities, add the following lines to the end of the
log4j2.propertiesconfiguration file in theES_PATH_CONF:logger.authc.name = org.elasticsearch.xpack.security.authc logger.authc.level = DEBUG
A successful authentication should produce debug statements that list groups and role mappings.