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

Posted to dev@ranger.apache.org by "Nitin Galave (JIRA)" <ji...@apache.org> on 2018/04/16 04:16:00 UTC

[jira] [Updated] (RANGER-1985) Auditing for Ranger Usersync operations

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

Nitin Galave updated RANGER-1985:
---------------------------------
    Attachment: RANGER-1985-UI-improvements.patch

> Auditing for Ranger Usersync operations
> ---------------------------------------
>
>                 Key: RANGER-1985
>                 URL: https://issues.apache.org/jira/browse/RANGER-1985
>             Project: Ranger
>          Issue Type: New Feature
>          Components: Ranger, usersync
>            Reporter: Sailaja Polavarapu
>            Assignee: Nitin Galave
>            Priority: Major
>             Fix For: 1.1.0
>
>         Attachments: 0001-RANGER-1985-Auditing-for-Ranger-usersync-operations.patch, 0001-RANGER-1985-Code-changes-to-support-follow-up-tasks-.patch, RANGER-1985-UI-improvements.patch, UI-RANGER-1985.patch
>
>
> During every sync cycle, ranger usersync should audit some basic information like number of users, number of groups that are sync'd for that cycle. Also provide details on sync source like the unix, file, or ldap with relevant configuration like ldap filters applied for that sync cycle, ldap host url, etc...
> Add a new tab in the ranger admin UI audits for usersync and show the above information.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)