This bug is created as a clone of upstream ticket:
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'.
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.
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.
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
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.