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 743505 - [RFE] Implement "AD friendly" schema mapping
Summary: [RFE] Implement "AD friendly" schema mapping
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.3
Hardware: All
OS: Linux
high
low
Target Milestone: beta
: 6.4
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks: 998474
TreeView+ depends on / blocked
 
Reported: 2011-10-05 07:19 UTC by Ondrej Valousek
Modified: 2020-05-02 16:27 UTC (History)
5 users (show)

Fixed In Version: sssd-1.9.1-1.el6
Doc Type: Enhancement
Doc Text:
Cause: Many RHEL customer use Active Directory which doesn't include POSIX attributes by defualt and use a custom attribute mapping which is different from the RFC2307bis standard. Consequence:Configuring SSSD as a client that fetched identities from AD was non trivial for administrators as they had to make sure POSIX attributes are present on the AD side and all attributes are correctly mapped. Change: The SSSD now includes a new Active Directory provider that contains the attribute mappings tailored specifically for use with Active Directory Result: When id_provider=ad is configured, the configuration no longer requires setting the attribute mappings manually.
Clone Of:
Environment:
Last Closed: 2013-02-21 09:34:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2073 0 None None None 2020-05-02 16:27:09 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 Ondrej Valousek 2011-10-05 07:19:38 UTC 
Active Directory implements RFC2307bis-like schema which looks like RFC2307bis, but it has a few exceptions. It would be nice to introduce something like:

ldap_schema=msrfc

which would be equivalent to:

ldap_user_object_class = user
ldap_group_object_class = group
ldap_user_home_directory = unixHomeDirectory
ldap_schema = rfc2307bis
ldap_sasl_authid = <hostname>$@<REALM>

This would ease integration with Active Directory
Comment 3 Stephen Gallagher 2011-10-05 11:56:17 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/1031
Comment 7 Kaushik Banerjee 2012-11-19 09:10:21 UTC 
Verified in version 1.9.2-13

Output from beaker automation run:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: adschema_001 compare with sysdb, idmapping=true
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Stopping sssd: [  OK  ]
Starting sssd: [  OK  ]
[  OK  ]
:: [16:12:47] ::  Sleeping for 5 seconds
adschemauser01:*:770812610:770800513:GECOS1:/:
:: [   PASS   ] :: Running 'getent passwd adschemauser01'
adschemauser01
:: [   PASS   ] :: Running 'getent passwd adschemauser01 | awk -F: '{print $1}' | grep adschemauser01'
770812610
:: [   PASS   ] :: Running 'getent passwd adschemauser01 | awk -F: '{print $3}' | grep 770812610'
770800513
:: [   PASS   ] :: Running 'getent passwd adschemauser01 | awk -F: '{print $4}' | grep 770800513'
GECOS1
:: [   PASS   ] :: Running 'getent passwd adschemauser01 | awk -F: '{print $5}' | grep GECOS1'
uid=770812610(adschemauser01) gid=770800513(domain users) groups=770800513(domain users),770812609(adschemagroup01)
:: [   PASS   ] :: Running 'id adschemauser01'
:: [   PASS   ] :: ldap_user_name is same in ldap:adschemauser01 and sysdb:adschemauser01
:: [   FAIL   ] :: ldap_user_fullname is different in ldap:adschemauser01 and sysdb:GECOS1 Might fail due to ticket 1482 
:: [   PASS   ] :: ldap_user_uid_number is same in ldap:770812610 and sysdb:770812610
:: [   PASS   ] :: ldap_user_gid_number is same in ldap:770800513 and sysdb:770800513
:: [   PASS   ] :: ldap_user_gecos is same in ldap:GECOS1 and sysdb:GECOS1
:: [   PASS   ] :: ldap_user_home_directory is same in ldap: and sysdb:
:: [   PASS   ] :: ldap_user_shell is same in ldap: and sysdb:
:: [   PASS   ] :: ldap_user_principal is same in ldap:adschemauser01 and sysdb:adschemauser01
:: [   PASS   ] :: ldap_user_member_of is same in ldap:CN=adschemagroup01,CN=Users,DC=sssdad,DC=com and sysdb:CN=adschemagroup01,CN=Users,DC=sssdad,DC=com
:: [   PASS   ] :: ldap_user_modify_timestamp is same in ldap:20121116211150.0Z and sysdb:20121116211150.0Z
:: [   PASS   ] :: ldap_user_entry_usn is same in ldap:136295 and sysdb:136295
:: [   PASS   ] :: ldap_user_ad_account_expires is same in ldap:0 and sysdb:0
:: [   PASS   ] :: ldap_user_ad_user_account_control is same in ldap:512 and sysdb:512
adschemagroup01:*:770812609:adschemauser01
:: [   PASS   ] :: Running 'getent group adschemagroup01'
adschemagroup01
:: [   PASS   ] :: Running 'getent group adschemagroup01 | awk -F: '{print $1}' | grep adschemagroup01'
770812609
:: [   PASS   ] :: Running 'getent group adschemagroup01 | awk -F: '{print $3}' | grep 770812609'
adschemauser01
:: [   PASS   ] :: Running 'getent group adschemagroup01 | awk -F: '{print $4}' | grep adschemauser01'
:: [   PASS   ] :: ldap_group_name is same in ldap:adschemagroup01 and sysdb:adschemagroup01
:: [   PASS   ] :: ldap_group_gid_number is same in ldap:770812609 and sysdb:770812609
:: [   PASS   ] :: ldap_group_member is same in ldap:adschemauser01 and sysdb:adschemauser01
:: [   PASS   ] :: ldap_group_modify_timestamp is same in ldap:20121116211150.0Z and sysdb:20121116211150.0Z
:: [   PASS   ] :: ldap_group_entry_usn is same in ldap:136297 and sysdb:136297


::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: adschema_002 compare with sysdb, idmapping=false
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Stopping sssd: [  OK  ]
Starting sssd: [  OK  ]
[  OK  ]
:: [16:13:07] ::  Sleeping for 5 seconds
adschemauser02:*:72002:72002:GECOS2:/home/adschemauser02:/bin/bash
:: [   PASS   ] :: Running 'getent passwd adschemauser02'
adschemauser02
:: [   PASS   ] :: Running 'getent passwd adschemauser02 | awk -F: '{print $1}' | grep adschemauser02'
72002
:: [   PASS   ] :: Running 'getent passwd adschemauser02 | awk -F: '{print $3}' | grep 72002'
72002
:: [   PASS   ] :: Running 'getent passwd adschemauser02 | awk -F: '{print $4}' | grep 72002'
GECOS2
:: [   PASS   ] :: Running 'getent passwd adschemauser02 | awk -F: '{print $5}' | grep GECOS2'
/home/adschemauser02
:: [   PASS   ] :: Running 'getent passwd adschemauser02 | awk -F: '{print $6}' | grep /home/adschemauser02'
/bin/bash
:: [   PASS   ] :: Running 'getent passwd adschemauser02 | awk -F: '{print $7}' | grep /bin/bash'
uid=72002(adschemauser02) gid=72002(adschemagroup02) groups=72002(adschemagroup02)
:: [   PASS   ] :: Running 'id adschemauser02'
:: [   PASS   ] :: ldap_user_name is same in ldap:adschemauser02 and sysdb:adschemauser02
:: [   FAIL   ] :: ldap_user_fullname is different in ldap:adschemauser02 and sysdb:GECOS2 Might fail due to ticket 1482 
:: [   PASS   ] :: ldap_user_uid_number is same in ldap:72002 and sysdb:72002
:: [   PASS   ] :: ldap_user_gid_number is same in ldap:72002 and sysdb:72002
:: [   PASS   ] :: ldap_user_gecos is same in ldap:GECOS2 and sysdb:GECOS2
:: [   PASS   ] :: ldap_user_home_directory is same in ldap:/home/adschemauser02 and sysdb:/home/adschemauser02
:: [   PASS   ] :: ldap_user_shell is same in ldap:/bin/bash and sysdb:/bin/bash
:: [   PASS   ] :: ldap_user_principal is same in ldap:adschemauser02 and sysdb:adschemauser02
:: [   PASS   ] :: ldap_user_member_of is same in ldap:CN=adschemagroup02,CN=Users,DC=sssdad,DC=com and sysdb:CN=adschemagroup02,CN=Users,DC=sssdad,DC=com
:: [   PASS   ] :: ldap_user_modify_timestamp is same in ldap:20121116211154.0Z and sysdb:20121116211154.0Z
:: [   PASS   ] :: ldap_user_entry_usn is same in ldap:136307 and sysdb:136307
:: [   PASS   ] :: ldap_user_ad_account_expires is same in ldap:0 and sysdb:0
:: [   PASS   ] :: ldap_user_ad_user_account_control is same in ldap:512 and sysdb:512
adschemagroup02
:: [   PASS   ] :: Running 'getent group adschemagroup02 | awk -F: '{print $1}' | grep adschemagroup02'
72002
:: [   PASS   ] :: Running 'getent group adschemagroup02 | awk -F: '{print $3}' | grep 72002'
adschemauser02
:: [   PASS   ] :: Running 'getent group adschemagroup02 | awk -F: '{print $4}' | grep adschemauser02'
:: [   PASS   ] :: ldap_group_name is same in ldap:adschemagroup02 and sysdb:adschemagroup02
:: [   PASS   ] :: ldap_group_gid_number is same in ldap:72002 and sysdb:72002
:: [   PASS   ] :: ldap_group_member is same in ldap:adschemauser02 and sysdb:adschemauser02
:: [   PASS   ] :: ldap_group_modify_timestamp is same in ldap:20121116211154.0Z and sysdb:20121116211154.0Z
:: [   PASS   ] :: ldap_group_entry_usn is same in ldap:136309 and sysdb:136309
Comment 8 errata-xmlrpc 2013-02-21 09:34:22 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.