ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivér Szabó (JIRA) <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18039) Ldap sync filter logged out after the ldapsearch query happens
Date Fri, 05 Aug 2016 09:25:20 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olivér Szabó updated AMBARI-18039:
----------------------------------
    Summary: Ldap sync filter logged out after the ldapsearch query happens  (was: Ldap sync
filter logged after the ldapsearch query happens)

> Ldap sync filter logged out after the ldapsearch query happens
> --------------------------------------------------------------
>
>                 Key: AMBARI-18039
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18039
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-18039.patch
>
>
> With TRACE log level, one of the filter logged out after the ldapsearch query happens,
that can cause if the ldapsearch query fails, then we cannot see the used query/filter in
the logs



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

Mime
View raw message