hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13526) Add detailed logging in KMS for the authentication failure of proxy user
Date Tue, 23 Aug 2016 01:11:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xiao Chen updated HADOOP-13526:
-------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.0-alpha1
                   2.9.0
           Status: Resolved  (was: Patch Available)

I have committed this to trunk and branch-2.

Thank you [~sacharya] for the contribution, and [~anu] for the review!

> Add detailed logging in KMS for the authentication failure of proxy user
> ------------------------------------------------------------------------
>
>                 Key: HADOOP-13526
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13526
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: kms
>         Environment: RHEL
>            Reporter: Suraj Acharya
>            Assignee: Suraj Acharya
>            Priority: Minor
>             Fix For: 2.9.0, 3.0.0-alpha1
>
>         Attachments: HADOOP-13526.patch, HADOOP-13526.patch.1, HADOOP-13526.patch.2,
HADOOP-13526.patch.3
>
>
> Problem :
> User A was not able to write a file to HDFS Encryption Zone. It was resolved by adding
proxy user A in kms-site.xml
> However, the logs showed :
> {code}2016-08-10 19:32:08,954 DEBUG org.apache.hadoop.security.authentication.server.AuthenticationFilter:
Request https://vm.example.com:16000/kms/v1/keyversion/aMxsSSKmMEzINTIrKURpFJgHnZxiOvsT9L1nMpbUoGu/_eek?eek_op=decrypt&doAs=userb&user.name=usera
user [usera] authenticated{code}
> Possible Solution :
> So the message which says the user was successfully authenticated comes from {{AuthenticationFilter.java}}.
However, when the filter on {{DelegationTokenAuthenticationFilter}} is called it hits an exception
there and there is no log message there. This leads to the confusion that we have had a success
while the exception happens in the next class.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message