[
https://issues.apache.org/jira/browse/RANGER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140635#comment-15140635
]
Gautam Borad commented on RANGER-205:
-------------------------------------
As per RANGER-204 : Delete User/Group Rest will have 'forceDelete' queryParam.
* If 'forceDelete' is true then User/group and their references shall be
deleted permanently from db.
* If 'forceDelete' is false and if there are any references of provided
User/Group then User/Group visibility shall be set to 'Hidden'.
* If 'forceDelete' is false and there are no references then system will try to
permanently delete User/group from DB.
* If 'forceDelete' is not passed in request then it will be set to false.
Marking this as resolved, based on the implementation in RANGER-204.
> Delete rest api of User not deleting user completely from system
> ----------------------------------------------------------------
>
> Key: RANGER-205
> URL: https://issues.apache.org/jira/browse/RANGER-205
> Project: Ranger
> Issue Type: Bug
> Affects Versions: 0.4.0
> Reporter: Hanish Bansal
> Assignee: Gautam Borad
> Fix For: 0.5.1, 0.6.0
>
>
> Delete rest api of user is removing entry from x_user table of database and
> not from x_portal_user table so user get invisible from UI and api return
> success status.
> Due to which if a user is updated to have username/email-id of deleted user,
> it will error message that this username/email-id already exists.
> Also if a new user is created with user-name of deleted user, user get
> successfully created but his/her details are mapped with deleted user.
> Rest apis used are:
> {quote}
> DELETE http://<ip>:6080/service/xusers/users/userName/<username>
> DELETE http://<ip>:6080/service/xusers/users/<id>
> {quote}
> Expected result:
> Apis should remove entry from both tables x_user and x_portal_user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
