RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 832120 - [RFE] Add AD provider
Summary: [RFE] Add AD provider
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-14 14:54 UTC by Stephen Gallagher
Modified: 2020-05-02 16:55 UTC (History)
3 users (show)

Fixed In Version: sssd-1.9.1-1.el6
Doc Type: Enhancement
Doc Text:
Cause: SSSD versions prior to 1.9 would typically use id_provider=ldap when connecting to Active Directory. That configuration required quite some tweaking and couldn't use the advanced features that are AD specific. Consequence: Configuring the SSSD as an AD client required AD knowledge and the performance was not optimal Change: A new provider for the SSSD was implemented Result: The administrator can set up AD client without having to know the specific AD attribute mappings and performance of AD provider is better especially during login than performance of LDAP provider.
Clone Of:
Environment:
Last Closed: 2013-02-21 09:26:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2419 0 None None None 2020-05-02 16:55:10 UTC
Red Hat Product Errata RHSA-2013:0508 0 normal SHIPPED_LIVE Low: sssd security, bug fix and enhancement update 2013-02-20 21:30:10 UTC

Description Stephen Gallagher 2012-06-14 14:54:30 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1377

For simplicity of setup, we should build an AD provider that will carry the configuration necessary to communicate with an Active Directory 2008 R2 server or later, using ID-mapping and with Kerberos for authentication.

This would mostly be a roll-up of functionality from the LDAP and Kerberos providers (similar to the IPA provider), while providing some specialized options such as 'ad_server' and 'ad_domain'.
Comment 1 RHEL Program Management 2012-07-10 07:06:10 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2 RHEL Program Management 2012-07-11 02:06:41 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 4 Kaushik Banerjee 2012-11-16 08:48:54 UTC 
Verified in version 1.9.2-13

Report from the beaker automation run:
[   PASS   ]      adprovider_001 ad_server = resolvable hostname
[   PASS   ]      adprovider_002 ad_server = hostname not resolvable
[   PASS   ]      adprovider_003 ad_server = _srv_
[   PASS   ]      adprovider_004 ad_server = <blank> defaults to _srv_
[   PASS   ]      adprovider_005 ad_server = IP
[   PASS   ]      adprovider_006 ad_domain = SSSDAD.COM
[   PASS   ]      adprovider_007 ad_domain = junk and first entry in keytab in valid
[   PASS   ]      adprovider_008 ad_domain = junk and first entry in keytab is invalid
[   PASS   ]      adprovider_009 ad_domain = <blank> should default to sssd domain
[   PASS   ]      adprovider_010 ad_hostname = hostname
[   PASS   ]      adprovider_011 krb5_keytab = /etc/krb5.keytab.keytabdoesntexist
[   PASS   ]      adprovider_012 keytab exists in non-default location
[   PASS   ]      adprovider_013 ldap_id_mapping=false
[   PASS   ]      adprovider_014 Change user password
[   PASS   ]      adprovider_015 User must change password on next logon
[   PASS   ]      adprovider_016 User account disabled
[   PASS   ]      adprovider_017 User account is expired
Comment 5 errata-xmlrpc 2013-02-21 09:26:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0508.html
Note You need to log in before you can comment on or make changes to this bug.