[ https://issues.apache.org/jira/browse/RANGER-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267339#comment-14267339
]
Don Bosco Durai commented on RANGER-205:
----------------------------------------
Seems we are getting quit a few use cases we need to address. I have created a wiki page to
consolidate the requirement and design. https://cwiki.apache.org/confluence/display/RANGER/Deleting+Users+and+Groups+from+Ranger+Admin
[~gautamborad], can you take the first cut?
I feel, we should still discuss the requirement and design in this JIRA, and use the wiki
page just to reflect the final decisions.
Thanks
> 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
>
> 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)
|