[
https://issues.apache.org/jira/browse/RANGER-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032078#comment-15032078
]
Madhan Neethiraj commented on RANGER-748:
-----------------------------------------
+1 for the patch. Please commit the fix in master and ranger-0.5 branches.
> Users in policy got changed after upgrade
> -----------------------------------------
>
> Key: RANGER-748
> URL: https://issues.apache.org/jira/browse/RANGER-748
> Project: Ranger
> Issue Type: Bug
> Components: admin, usersync
> Affects Versions: 0.5.1
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 0.5.1, 0.6.0
>
> Attachments: RANGER-748.patch
>
>
> *Issue*
> After upgrading ranger from older version to latest : Users in x_user and
> x_portal_user tables are not in sync and due to this policies populates wrong
> users after upgrade and service check of plugin components fails.
> *Root cause*
> As part of [commit |
> https://github.com/apache/incubator-ranger/commit/7c185e1f5a8881fd7a7ad0d60abd756b3cd416ec]
> - RangerPolicyRetriever.java [Line No: 253]. Code is to read username
> using userId. In this function, userId being passed is of x_user table but
> code written is to read it from x_portal_user.
> So when IDs in x_user and x_portal_user are not in sync, this code will
> return wrong username, and that's why username in policies will be changed
> with some other username.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
