[
https://issues.apache.org/jira/browse/RANGER-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151537#comment-15151537
]
rangerqa commented on RANGER-803:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12788278/0001-Ranger-803-Rebuild-the-patch-with-latest-merge-from-.patch
against master revision b1ff479.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
+1 checkstyle. The patch generated 0 code style errors.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-RANGER-Build/61//testReport/
Console output: https://builds.apache.org/job/PreCommit-RANGER-Build/61//console
This message is automatically generated.
> Support multiple OU in LDAP search for Ranger usersync
> ------------------------------------------------------
>
> Key: RANGER-803
> URL: https://issues.apache.org/jira/browse/RANGER-803
> Project: Ranger
> Issue Type: New Feature
> Components: usersync
> Affects Versions: 0.5.0, 0.5.1
> Reporter: Sailaja Polavarapu
> Assignee: Sailaja Polavarapu
> Fix For: 0.6.0
>
> Attachments:
> 0001-Ranger-803-Rebuild-the-patch-with-latest-merge-from-.patch,
> MultipleOULdapSearchsupportforUserSync.docx
>
>
> Ranger should be able to search multiple OU in AD. For example, one OU could
> be for business users, other OU could be for Hadoop service users. Ranger
> would need to sync with both to create policies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
