Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-21910

Ranger Usersync config to support nested group evaluation for LDAP Sync source property

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.6.0
    • trunk, 2.6.0
    • ambari-server
    • None

    Description

      As part of RANGER-1735, we are supporting nested groups in ranger usersync. For this, introduced one new property "ranger.usersync.ldap.grouphierarchylevels". The value should be an integer with default value as 0. This property should be under Ranger --> Configs --> Ranger User Info --> Group Configs tab.
      This property can be enabled with a flag labelled as "Sync Nested Groups".
      1. Default value for this flag is "No"
      2. This flag is always shown under Group Configs (even when "Enable group Sync" is set to "No")
      3. If this flag is set to "No", then the value for ranger.usersync.ldap.grouphierarchylevels is hidden and is set to "0".
      4. If this flag is set to "Yes", then ranger.usersync.ldap.grouphierarchylevels is shown and allowed to set any integer greater than 0.

      Attachments

        1. AMBARI-21910.patch
          13 kB
          Mugdha Varadkar
        2. AMBARI-21910-01-branch-2.6.patch
          17 kB
          Mugdha Varadkar
        3. AMBARI-21910-01-trunk.patch
          21 kB
          Mugdha Varadkar
        4. AMBARI-21910-02-branch-2.6.patch
          17 kB
          Mugdha Varadkar
        5. AMBARI-21910-02-trunk.patch
          21 kB
          Mugdha Varadkar

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mugdha.varadkar Mugdha Varadkar
            mugdha.varadkar Mugdha Varadkar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment