[
https://issues.apache.org/jira/browse/RANGER-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
bharath updated RANGER-2572:
----------------------------
Description:
Hi Team,
# We have a requirement to add/update/delete a user to a group in ranger
through rest API. I see that there are rest API available using the userId but
not through userName. Is there any way we can do this ??
# Also while creating a user the id that is given in JSON request is not
taken, instead ranger creates its own id for the user and gives it back as a
response. Is there a way to force ranger the id that I provide. But even this
id is not seen anywhere in the ranger UI.
was:
Hi Team,
# We have a requirement to add/update/delete a user to a group in ranger
through rest API. I see that there are rest API available using the userId but
not through userName. Is there any way we can do this ??. I see that there are
ways to do this by using userID field.
# Also while creating a user the id that is given in JSON request is not
taken, instead ranger creates its own id for the user and gives it back as a
response. Is there a way to force ranger the id that I provide. But even this
id is not seen anywhere in the ranger UI.
> Unable to update/add user to group with userName using rest API.
> ----------------------------------------------------------------
>
> Key: RANGER-2572
> URL: https://issues.apache.org/jira/browse/RANGER-2572
> Project: Ranger
> Issue Type: New Feature
> Components: Ranger
> Affects Versions: 1.2.0
> Reporter: bharath
> Priority: Critical
> Labels: features
>
> Hi Team,
> # We have a requirement to add/update/delete a user to a group in ranger
> through rest API. I see that there are rest API available using the userId
> but not through userName. Is there any way we can do this ??
> # Also while creating a user the id that is given in JSON request is not
> taken, instead ranger creates its own id for the user and gives it back as a
> response. Is there a way to force ranger the id that I provide. But even this
> id is not seen anywhere in the ranger UI.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
