Bug 1474711
| Summary: | Querying the AD domain for external domain's ID can mark the AD domain offline | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jakub Hrozek <jhrozek> | |
| Component: | sssd | Assignee: | SSSD Maintainers <sssd-maint> | |
| Status: | CLOSED ERRATA | QA Contact: | ipa-qe <ipa-qe> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.3 | CC: | ekeck, fidencio, grajaiya, hkhot, jhrozek, jnansi, lslebodn, mkosek, mzidek, ndehadra, pbrezina, sgoveas, tscherf | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | sssd-1.16.0-1.el7 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1478252 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-10 17:13:24 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1478252 | |||
|
Description
Jakub Hrozek
2017-07-25 08:54:15 UTC
* master: a406b52a0d20e0ec502f52d63dee293636d1443a I'd like to propose this bug for 7.4.1, because it would be really inconvenient for admins and impossible to debug for support engineers to find out why are their AD domains going offline. The steps to reproduce are: 1) configure IPA-AD trust with POSIX attributes 2) revert the domain order lookup so that the AD domains are checked first 3) run 'id' for the IPA user (maybe it would be even simpler to check if just running getent passwd -s sss $some_random_id also takes the provider offline, but I didn't check that. If yes, the bug would be just more severe) IPA VERSION: ipa-server-4.5.4-6.el7.x86_64 SSSD VERSION: sssd-1.16.0-9.el7.x86_64 IPA CLIENT VERSION : ipa-client-4.5.4-6.el7.x86_64 Verified the bug on the basis of following observations: ON IPA-MASTER: ----------------- [root@auto-hv-01-guest10 ~]# rpm -q ipa-server sssd ipa-client ipa-server-4.5.4-6.el7.x86_64 sssd-1.16.0-9.el7.x86_64 ipa-client-4.5.4-6.el7.x86_64 [root@auto-hv-01-guest10 ~]# echo <password> | ipa trust-add pne.qe --admin Administrator --range-type=ipa-ad-trust-posix --password --two-way=True ----------------------------------------------- Added Active Directory trust for realm "pne.qe" ----------------------------------------------- Realm name: pne.qe Domain NetBIOS name: PNE Domain Security Identifier: S-1-5-21-2202318585-426110948-4011710778 Trust direction: Two-way trust Trust type: Active Directory domain Trust status: Established and verified [root@auto-hv-01-guest10 ~]# ipa idrange-find ---------------- 2 ranges matched ---------------- Range name: ND0612171.TEST_id_range First Posix ID of the range: 1837800000 Number of IDs in the range: 200000 First RID of the corresponding RID range: 1000 First RID of the secondary RID range: 100000000 Range type: local domain range Range name: PNE.QE_id_range First Posix ID of the range: 1261600000 Number of IDs in the range: 200000 Domain SID of the trusted domain: S-1-5-21-2202318585-426110948-4011710778 Range type: Active Directory trust range with POSIX attributes ---------------------------- Number of entries returned 2 ---------------------------- [root@auto-hv-01-guest10 ~]# id aduser1 uid=10000(aduser1) gid=454547(adgroup1) groups=454547(adgroup1),454548(adgroup2) [root@auto-hv-01-guest10 ~]# ipa config-mod --domain-resolution-order='pne.qe:nd0612171.test' Maximum username length: 32 Home directory base: /home Default shell: /bin/sh Default users group: ipausers Default e-mail domain: nd0612171.test Search time limit: 2 Search size limit: 100 User search fields: uid,givenname,sn,telephonenumber,ou,title Group search fields: cn,description Enable migration mode: FALSE Certificate Subject base: O=ND0612171.TEST Password Expiration Notification (days): 4 Password plugin features: AllowNThash, KDC:Disable Last Success SELinux user map order: guest_u:s0$xguest_u:s0$user_u:s0$staff_u:s0-s0:c0.c1023$unconfined_u:s0-s0:c0.c1023 Default SELinux user: unconfined_u:s0-s0:c0.c1023 Default PAC types: MS-PAC, nfs:NONE IPA masters: auto-hv-01-guest10.nd0612171.test IPA CA servers: auto-hv-01-guest10.nd0612171.test IPA NTP servers: auto-hv-01-guest10.nd0612171.test IPA CA renewal master: auto-hv-01-guest10.nd0612171.test IPA master capable of PKINIT: auto-hv-01-guest10.nd0612171.test Domain resolution order: pne.qe:nd0612171.test [root@auto-hv-01-guest10 ~]# id admin uid=1837800000(admin) gid=1837800000(admins) groups=1837800000(admins) ON IPA-CLIENT: ---------------- [root@auto-hv-01-guest06 ~]# getent passwd -s sss 120000 aduser1:*:120000:454547:aduser1:/home/aduser1:/bin/sh [root@auto-hv-01-guest06 ~]# getent passwd -s sss aduser1 aduser1:*:120000:454547:aduser1:/home/aduser1:/bin/sh [root@auto-hv-01-guest06 ~]# cat /var/log/sssd/sssd.log | grep -i "OFFLINE" [root@auto-hv-01-guest06 ~]# cat /var/log/sssd/sssd_nd0612171.test.log | grep -i "OFFLINE" (Wed Dec 6 04:12:03 2017) [sssd[be[nd0612171.test]]] [dp_get_options] (0x0400): Option ldap_offline_timeout has value 60 (Wed Dec 6 04:12:03 2017) [sssd[be[nd0612171.test]]] [dp_get_options] (0x0400): Option krb5_store_password_if_offline is TRUE [root@auto-hv-01-guest06 ~]# cat /var/log/sssd/sssd.log| grep "ad_account_can_shortcut" [root@auto-hv-01-guest06 ~]# cat /var/log/sssd/sssd_nd0612171.test.log| grep "ad_account_can_shortcut" Thus on the basis of above observations marking status of bug to "VERIFIED" Hello Jakub, sssd engineering team, I have a customer encountering this bug, can I get a test package to verify fix? Jatin (In reply to Jatin Nansi from comment #9) > Hello Jakub, sssd engineering team, > > I have a customer encountering this bug, can I get a test package to verify > fix? > > Jatin Yes, the fix is backportable. Can you give me the exact version to create the backport atop? 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. https://access.redhat.com/errata/RHEA-2018:0929 |