[jira] [Commented] (AMBARI-12627) Ambari 2.0 -> 2.1 LDAP: error code 12

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-12627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653031#comment-14653031 ] 

Hadoop QA commented on AMBARI-12627:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12748567/AMBARI-12627.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.security.ldap.AmbariLdapDataPopulatorTest

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3519//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3519//console

This message is automatically generated.

> Ambari 2.0 -> 2.1 LDAP: error code 12
> -------------------------------------
>
>                 Key: AMBARI-12627
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12627
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12627.patch
>
>
> LDAP result pagination works well for large amounts of users needing to be synchronized from Active Directory, which is the  common LDAP implementation. For those using ODSEE 11g, however, it's unsupported. 
> For this reason, it would be beneficial to make this pagination option configurable.
> For turning off ldap search results pagination add authentication.ldap.pagination.enabled=false into ambari.properties file



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)