You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Ramesh Mani (Jira)" <ji...@apache.org> on 2022/04/16 05:38:00 UTC

[jira] [Updated] (RANGER-3505) Ranger usersync fails to sync users when a duplicate user exists in ranger

     [ https://issues.apache.org/jira/browse/RANGER-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Mani updated RANGER-3505:
--------------------------------
    Fix Version/s: 2.3.0

> Ranger usersync fails to sync users when a duplicate user exists in ranger
> --------------------------------------------------------------------------
>
>                 Key: RANGER-3505
>                 URL: https://issues.apache.org/jira/browse/RANGER-3505
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger, usersync
>            Reporter: Sailaja Polavarapu
>            Assignee: Sailaja Polavarapu
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: 0001-RANGER-3505-modified-code-to-ignore-case-while-valid.patch
>
>
> Ranger is having issue with syncing user with case sensitive when the backend database for ranger is MySQL / Maria DB. Initially users are sync'd with default configuration (without any case conversion). Later usersync is configured to sync users with upper case. At this time, usersync fails to sync any users throwing duplicate user exception. For resolving this, existing user from ranger must be deleted and then restarted the usersync service. Instead, ranger code should update existing user with case conversion and continue.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)