#2142 AD Enumeration reads data from LDAP while regular lookups connect to GC
Closed: Fixed Opened by jhrozek.

We have a bad inconsistency when performing lookups. When enumerating users and groups, we connect to LDAP port automatically, while when doing regular lookups, we connect to GC.

This can have very confusing consequences if POSIX attributes are requested but not replicated to GC -- the users that are enumerated will show up with POSIX attributes, but since initgroups are performed against GC, the attributes not present in GC but present in LDAP are deleted from sysdb.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.3

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1028039

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1028039 1028039]

Fields changed

owner: somebody => jhrozek

Fields changed

patch: 0 => 1

Fields changed

milestone: SSSD 1.11.3 => SSSD 1.11.4

  • master:
    • b4ffa4d19e912740af6df3c1a4fabcea69729885
    • 37171a92dc9c5e4fe1a0663901fc965b49a78151
    • 12213ca982ee3ad58f08e145532b500d7c4678d1
    • dde2f0b4fcabc7093ddfcdda3dbacff00b82df46
    • 19fd860d78256a4ab5a268cd58337a8bd2920ceb
    • f8407faaeb6726bef6463d84f183f2b0ad1f99d4
    • 21767bbb68c826b0bbd9ff55db28375f6681b9fb
  • sssd-1-11:
    • 580221eebb363fcda33d17f513f54752787bb829
    • 407a7e05f9077ccaefe5412f794347e4c9da94bb
    • ff4ca560f597303c62b83cc484f33e114e52ba0a
    • 8c127026dccada5b00b84829236914219b538f22
    • c5ae054095bed216cb70f3b929b3ac5497bc260a
    • e0502a6c5bc30415c372e9e6e835b94b04d5195a
    • 02abb93af0c81da869766c8302aecf3d08aa47e0

resolution: => fixed
status: new => closed

Fields changed

changelog: => Regular user lookups and enumeration task that runs in the background used a different Active Directory server port for the lookups which might have resulted in inconsistent results when requesting user and/or group information.

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.11.4

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3184

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata