[ https://issues.apache.org/jira/browse/RANGER-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhishek Kumar resolved RANGER-4230. ------------------------------------ Resolution: Fixed [Commit|https://github.com/apache/ranger/commit/67ab95f40d7021839679a5c99096e33359e99582] > New REST APIs for force deletes of users & groups > ------------------------------------------------- > > Key: RANGER-4230 > URL: https://issues.apache.org/jira/browse/RANGER-4230 > Project: Ranger > Issue Type: New Feature > Components: Ranger > Affects Versions: 2.4.0 > Reporter: Abhishek Kumar > Assignee: Abhishek Kumar > Priority: Major > Fix For: 3.0.0 > > Original Estimate: 336h > Time Spent: 2h > Remaining Estimate: 334h > > Ranger admin should have an option to clean up all external users/groups from > ranger DB. > Due to incorrect ranger usersync configuration, specially using LDAP/AD, > large number of users and groups end up in ranger. > Large user/group and mapping tables have the potential to cause issues > related to ranger admin OOM. Existing REST APIs for deletion are slow and > only allow one user/group deletion at a time. > A Ranger API option to clean up external user and groups (or bulk delete > user/groups) will be much helpful to address the issues indicated above. > This Jira only tracks changes for the REST API, a UI option can also be > enabled as part another Jira to use the same functionality. -- This message was sent by Atlassian Jira (v8.20.10#820010)