[jira] [Resolved] (AMBARI-24226) Ambari ldap integration has inconsistent behavior in Group Object Class definition after upgrade

["Attila Magyar (JIRA)" <ji...@apache.org>]

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

Attila Magyar resolved AMBARI-24226.
------------------------------------
    Resolution: Fixed

> Ambari ldap integration has inconsistent behavior in Group Object Class definition after upgrade
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24226
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24226
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Attila Magyar
>            Assignee: Attila Magyar
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The behavior of the ambari ldap integration seems inconsistent across 2.6.2 -> 2.7.0 upgrade.
> In Ambari 2.6.2, the Group Object Class property is exemplified as taking what is commonly known as the group object class attribute.
> Group object class* (posixGroup):
> In Ambari 2.7.0, the Group Object Class property is exemplified as taking what is commonly known as the group search base.
> Group object class* (ou=groups,dc=ambari,dc=apache,dc=org):
> The first one is the correct.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)