Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2152

• Created at 2013-11-14 20:25:25 by jhrozek
• Closed as Fixed
• Assigned to jhrozek
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1033081

20:19 < simo> jhrozek: right after we search rootdse make a search for (uidNumber=*) under cn=users
20:19 < simo> if anything is returned we know it is ok to stay with gc
20:19 < simo> otherwise we disconnect, and switch to normal LDAP
20:19 < simo> we can use a control to limit how many entries are returned too
20:20 < simo> using the paged search and telling AD to return 5 entries pages or so
20:20 < simo> so we do not have to process a ton of data just for probing

Comments

Comment from jhrozek at 2013-11-14 20:25:43

Fields changed

description: 20:19 < simo> jhrozek: right after we search rootdse make a search for (uidNumber=) under cn=users
20:19 < simo> if anything is returned we know it is ok to stay with gc
20:19 < simo> otherwise we disconnect, and switch to normal LDAP
20:19 < simo> we can use a control to limit how many entries are returned too
20:20 < simo> using the paged search and telling AD to return 5 entries pages or so
20:20 < simo> so we do not have to process a ton of data just for probing
=> {{{
20:19 < simo> jhrozek: right after we search rootdse make a search for (uidNumber=) under cn=users
20:19 < simo> if anything is returned we know it is ok to stay with gc
20:19 < simo> otherwise we disconnect, and switch to normal LDAP
20:19 < simo> we can use a control to limit how many entries are returned too
20:20 < simo> using the paged search and telling AD to return 5 entries pages or so
20:20 < simo> so we do not have to process a ton of data just for probing
}}}

Comment from jhrozek at 2013-11-19 16:22:22

This is quite important, several users complained about us switching all lookups to GC by default already. Picking up.

owner: somebody => jhrozek
status: new => assigned

Comment from dpal at 2013-11-21 15:15:43

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.3

Comment from dpal at 2013-11-21 15:16:27

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

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

Comment from jhrozek at 2013-12-19 10:06:49

Moving tickets that didn't make 1.11.3 to 1.11.4

milestone: SSSD 1.11.3 => SSSD 1.11.4

Comment from jhrozek at 2014-01-28 15:13:02

Fields changed

patch: 0 => 1

Comment from jhrozek at 2014-02-12 15:32:46

• master: 86c2e80
• sssd-1-11: e81deec

resolution: => fixed
status: assigned => closed

Comment from jhrozek at 2014-02-17 20:23:31

Fields changed

changelog: => The SSSD is able to detect if POSIX attributes were replicated to the Global Catalog. If not, the administrator is warned with a DEBUG message and the SSSD switches to LDAP lookups.

Comment from jhrozek at 2017-02-24 14:59:41

Metadata Update from @jhrozek:

• Issue assigned to jhrozek
• Issue set to the milestone: SSSD 1.11.4