[AMBARI-17444] LDAP sync: use uid and cn in patterns to check a member is a dn or not and small fixes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Assignee: Oliver Szabo
• Reporter: Oliver Szabo
• Created: 26/Jun/16 15:55
• Updated: 28/Jun/16 16:19
• Resolved: 28/Jun/16 13:19

Description

• fix member dn format check
• add new attribute: authorization.ldap.adminGroupMappingMemberAttr what can be used during adminGroupMapping rules filter (the filter starts with e.g. : member= {dn}

  ...if memberUid is used, dn is not right, so you can use custom attribute here, like: uid)

Issue Links

• links to: Review Board