You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "xiaojunxiang (Jira)" <ji...@apache.org> on 2024/03/29 02:08:00 UTC
[jira] [Updated] (HDFS-17447) Add logging to print the implementation class of AccessControlEnforcer, print ACEnforcer when AccessControlException occurs.
[ https://issues.apache.org/jira/browse/HDFS-17447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
xiaojunxiang updated HDFS-17447:
--------------------------------
Summary: Add logging to print the implementation class of AccessControlEnforcer, print ACEnforcer when AccessControlException occurs. (was: Add an implementation class that prints AccessControlEnforcer when an ACE exception occurs.)
> Add logging to print the implementation class of AccessControlEnforcer, print ACEnforcer when AccessControlException occurs.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17447
> URL: https://issues.apache.org/jira/browse/HDFS-17447
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Reporter: xiaojunxiang
> Priority: Major
> Labels: pull-request-available
>
> As we know, when Ranger authentication is enabled in the HDFS, if Ranger authentication fails to match, it is degraded to the FSPermissionChecker authentication of the HDFS ACL.
> If an ACE occurs, it is not clear whether it comes from Ranger authentication or FSPermissionChecker authentication. So I think we should add a description of AccessControlEnforcer to the ACE exception description to help locate the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org