ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-12627) Ambari 2.0 -> 2.1 LDAP: error code 12
Date Tue, 04 Aug 2015 11:50:04 GMT


Hadoop QA commented on AMBARI-12627:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 1 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 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 ambari-server.

Test results:
Console output:

This message is automatically generated.

> Ambari 2.0 -> 2.1 LDAP: error code 12
> -------------------------------------
>                 Key: AMBARI-12627
>                 URL:
>             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_2.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 file

This message was sent by Atlassian JIRA

View raw message