Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 991685

Summary: [RFE] Add ability to specify LDAP schema in order to be able to use Active Directory
Product: [Retired] Pulp Reporter: redbugzilla
Component: user-experienceAssignee: Sayli Karmarkar <skarmark>
Status: CLOSED UPSTREAM QA Contact: Preethi Thomas <pthomas>
Severity: medium Docs Contact:
Priority: medium    
Version: MasterCC: cperry, rbarlow
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-19 01:11:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 817063    
Bug Blocks:    

Description redbugzilla 2013-08-03 15:42:28 UTC
Description of problem:
There is already an RFE for specifying bind credentials, however the code assumes that username (for example) will match against an attribute called "uid".
See the ldap_filter in the function lookup_user in pulp/platform/src/pulp/server/auth/

This may not be true for all LDAP servers, for example Active Directory.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Have an LDAP server where username is not in an attribute called "uid"
2. LDAP authentication wont work because the user wont be found.

Actual results:
Can't actually get this far, because we can't bind to AD with credentials yet.

Expected results:
Specify uid attribute as sAMAccountName
and others too, like:
gecos = displayName

Additional info:
Need to link this up with Bug 817063, since there is no point getting this done before that one; well for AD support anyway.

Comment 1 Brian Bouterse 2015-02-19 01:11:44 UTC
Moved to