[
https://issues.apache.org/jira/browse/RANGER-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-980:
----------------------------------------
Fix Version/s: 2.2.0
3.0.0
> User sync does not delete users if they do not exist anymore
> ------------------------------------------------------------
>
> Key: RANGER-980
> URL: https://issues.apache.org/jira/browse/RANGER-980
> Project: Ranger
> Issue Type: Bug
> Components: usersync
> Affects Versions: 0.6.0, 0.5.3
> Reporter: Bolke de Bruin
> Assignee: Sailaja Polavarapu
> Priority: Critical
> Labels: security
> Fix For: 3.0.0, 2.2.0
>
> Attachments:
> 0001-RANGER-980-Support-for-deleted-users-groups-in-Range.patch,
> 0001-RANGER-980-User-sync-does-not-delete-users-if-they-d.patch, Deleted
> users and groups support in Ranger (RANGER-980).pdf, RANGER-980.patch
>
>
> usersync for all sources creates users and groups, but does not delete them
> from Ranger's database if these users and groups do not exists anymore in the
> original source.
> So if you have for example a user called "bob" and bob leaves the company his
> access rights will continue to exist in Ranger. If a new employee comes in
> that is also "bob" he is immediately granted the same access as the previous
> employee. This creates security incidents.
> In a reasonable complex company it cannot be expected that another user
> administration is being taken care of, while deletion could and should happen
> automatically.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
