You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Abhay Kulkarni (Jira)" <ji...@apache.org> on 2022/02/14 16:21:00 UTC

[jira] [Comment Edited] (RANGER-3522) Improve Tagsync authentication error reporting

    [ https://issues.apache.org/jira/browse/RANGER-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447723#comment-17447723 ] 

Abhay Kulkarni edited comment on RANGER-3522 at 2/14/22, 4:20 PM:
------------------------------------------------------------------

Commit details:

master:

[https://github.com/apache/ranger/commit/3f82858760e01ed186a2b3055c95b9cdd343db4b]

[https://github.com/apache/ranger/commit/03f6d3f18f8576d710928be4b148143b8a9f8d91]

 


was (Author: abhayk):
Commit details:

master:

https://github.com/apache/ranger/commit/3f82858760e01ed186a2b3055c95b9cdd343db4b

> Improve Tagsync authentication error reporting
> ----------------------------------------------
>
>                 Key: RANGER-3522
>                 URL: https://issues.apache.org/jira/browse/RANGER-3522
>             Project: Ranger
>          Issue Type: Bug
>          Components: tagsync
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: 3.0.0
>
>
> TagSync is expected to cause system exit if any kerberos authentication error is encountered. There might be situations where it starts without reporting any errors and hence no messages are processed. This needs to be investigated and fixed.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)