You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Sailaja Polavarapu (JIRA)" <ji...@apache.org> on 2017/05/04 18:08:04 UTC
[jira] [Commented] (RANGER-1475) some users missed to be sync if
they are syncd from openldap If deltasync is enabled
[ https://issues.apache.org/jira/browse/RANGER-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997147#comment-15997147 ]
Sailaja Polavarapu commented on RANGER-1475:
--------------------------------------------
Same patch can be applied to master and ranger-0.7 branches.
> some users missed to be sync if they are syncd from openldap If deltasync is enabled
> ------------------------------------------------------------------------------------
>
> Key: RANGER-1475
> URL: https://issues.apache.org/jira/browse/RANGER-1475
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 0.7.1
> Reporter: Deepak Sharma
> Assignee: Deepak Sharma
> Fix For: 1.0.0, 0.7.1
>
>
> some users missed to be sync if they are syncd from openldap in a scenario when users are added to the ldap at the time when usersync is happening or if it is in progress or within a minute of usersync cycle.
> {code}
> if (deltaSyncUserTime < highestdeltaSyncUserTime) {
> // Incrementing highestdeltaSyncUserTime (for AD) in order to avoid search record repetition for next sync cycle.
> deltaSyncUserTime = highestdeltaSyncUserTime+1;
> // Incrementing the highest timestamp value (for Openldap) with 1min in order to avoid search record repetition for next sync cycle.
> deltaSyncUserTimeStamp = dateFormat.format(new Date(highestdeltaSyncUserTime + 60000l));
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)