[
https://issues.apache.org/jira/browse/RANGER-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-2786:
------------------------------------
Attachment: 0001-RANGER-2786-Ranger-usersync-group-modifyTimestamp-pa.patch
> Ranger usersync group modifyTimestamp parsing should be in 24 hours format
> ---------------------------------------------------------------------------
>
> Key: RANGER-2786
> URL: https://issues.apache.org/jira/browse/RANGER-2786
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Pradeep Agrawal
> Assignee: Pradeep Agrawal
> Priority: Major
> Fix For: 2.1.0, 2.1
>
> Attachments:
> 0001-RANGER-2786-Ranger-usersync-group-modifyTimestamp-pa.patch
>
>
> *Problem Statement:* Currently Ranger usersync group modifyTimestamp parsing
> is in 12 hours format. (not sure its as per the requirement or by mistake).
> for the parsing date format is choosen as "yyyyMMddhhmmss" where hh can
> convert hour value to 12 hours format. for example: if a group is synced at
> 00:05am UTC then this will highest user sync time stamp but after the
> conversion value becomes 12:05 which is actually future timestamp and for the
> next 12 hours delta sync of groups may not sync any groups.
> *Proposed solution:* Conversion should be done in 24 hours format by using
> hours in HH format rather hh.
> *Note:* 1) To reproduce this issue frequently i have to switch my default
> ldap delta sync interval to 5 minute as compare to 1 hour.
> 2) I am not sure about the current behaviour of different ldap servers and AD
> without this patch. some might be working so i request reviewers to add their
> feedback on this.
> 3) It will be better if reviewers can test this patch in their environment
> and share their experiance here or on the jira.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
