Back to bug 1400614

Who When What Removed Added
RHEL Program Management 2016-12-01 15:50:18 UTC Keywords FutureFeature
German Parente 2016-12-01 15:55:09 UTC CC gparente
Jakub Hrozek 2016-12-08 16:15:24 UTC Status NEW ASSIGNED
Luc de Louw 2017-01-24 14:52:37 UTC CC ldelouw
Sumit Bose 2017-01-25 13:44:29 UTC CC sbose
Chris Williams 2017-03-08 17:44:15 UTC Blocks 1420851
Thorsten Scherf 2017-07-11 10:38:07 UTC Depends On 1467835
Thorsten Scherf 2017-07-11 10:41:49 UTC Blocks 1467835
Depends On 1467835
Martin Kosek 2017-07-21 07:21:10 UTC Blocks 1472344
Steeve Goveas 2017-08-21 15:07:51 UTC CC sgoveas
QA Contact sgoveas dlavu
Ellen Newlands 2017-08-21 16:59:34 UTC CC enewland
Martin Kosek 2017-09-11 13:46:07 UTC Blocks 1490412
Libor Miksik 2017-10-09 10:45:39 UTC Blocks 1477926
Aneta Šteflová Petrová 2017-10-20 08:12:09 UTC Blocks 1504554
Jakub Hrozek 2017-11-02 11:56:32 UTC Status ASSIGNED POST
Fabiano Fidêncio 2017-11-03 18:09:14 UTC Status POST MODIFIED
CC fidencio
Fixed In Version sssd-1.16.0-2.el7
errata-xmlrpc 2017-11-03 18:56:16 UTC Status MODIFIED ON_QA
Lenka Špačková 2017-11-09 14:41:32 UTC Docs Contact apetrova
Aneta Šteflová Petrová 2017-11-22 12:49:04 UTC Doc Type If docs needed, set a value Enhancement
Flags needinfo?(pbrezina)
Pavel Březina 2017-11-23 09:51:37 UTC Doc Text Feature: SSSD enrolled into an Active Directory domain will remember site on its first discovery.

Reason: In order to determine client's site, SSSD must send an LDAP ping to any domain controller first. If the chosen controller can't be reached for any reason it will result in a timeout which will delay the connection for several seconds. By remembering the site, we can speed up such situation by always contacting domain controller from the site which is supposed to be always reachable.

Result: Subsequent calls to LDAP ping are done always on domain controller from client's site, making those request faster.
Flags needinfo?(pbrezina)
Aneta Šteflová Petrová 2017-11-23 12:32:36 UTC Doc Text Feature: SSSD enrolled into an Active Directory domain will remember site on its first discovery.

Reason: In order to determine client's site, SSSD must send an LDAP ping to any domain controller first. If the chosen controller can't be reached for any reason it will result in a timeout which will delay the connection for several seconds. By remembering the site, we can speed up such situation by always contacting domain controller from the site which is supposed to be always reachable.

Result: Subsequent calls to LDAP ping are done always on domain controller from client's site, making those request faster.
SSSD enrolled to an AD domain remembers the discovered AD site after the first successful connection

Previously, the System Security Services Daemon (SSSD) sent an LDAP ping to an Active Directory (AD) domain controller in order to determine a client's AD site. If the controller was unreachable, a timeout occurred, which delayed the connection for several seconds. With this update, SSSD remembers the client's site after the first successful discovery. All subsequent LDAP pings are performed on the domain controller from the client's site, which helps speed up the request.
Flags needinfo?(pbrezina)
Pavel Březina 2017-11-23 13:21:17 UTC Flags needinfo?(pbrezina)
Aneta Šteflová Petrová 2017-11-23 14:06:44 UTC Doc Text SSSD enrolled to an AD domain remembers the discovered AD site after the first successful connection

Previously, the System Security Services Daemon (SSSD) sent an LDAP ping to an Active Directory (AD) domain controller in order to determine a client's AD site. If the controller was unreachable, a timeout occurred, which delayed the connection for several seconds. With this update, SSSD remembers the client's site after the first successful discovery. All subsequent LDAP pings are performed on the domain controller from the client's site, which helps speed up the request.
SSSD enrolled to an AD domain remembers the discovered AD site after the first successful connection

Previously, the System Security Services Daemon (SSSD) sent an LDAP ping to any Active Directory (AD) domain controller in order to determine a client's AD site. If the contacted controller was unreachable, a timeout occurred, which delayed the connection for several seconds. With this update, SSSD remembers the client's site after the first successful discovery. All subsequent LDAP pings are performed on the domain controller from the client's site, which helps speed up the request.
Aneta Šteflová Petrová 2017-11-24 09:11:29 UTC Doc Text SSSD enrolled to an AD domain remembers the discovered AD site after the first successful connection

Previously, the System Security Services Daemon (SSSD) sent an LDAP ping to any Active Directory (AD) domain controller in order to determine a client's AD site. If the contacted controller was unreachable, a timeout occurred, which delayed the connection for several seconds. With this update, SSSD remembers the client's site after the first successful discovery. All subsequent LDAP pings are performed on the domain controller from the client's site, which helps speed up the request.
SSSD enrolled to an AD domain remembers the discovered AD site after the first successful connection

Previously, the System Security Services Daemon (SSSD) sent an LDAP ping to any Active Directory (AD) domain controller (DC) in order to determine a client's AD site. If the contacted DC was unreachable, a timeout occurred, which delayed the connection for several seconds. With this update, SSSD remembers the client's site after the first successful discovery. All subsequent LDAP pings are performed on the DC from the client's site, which helps speed up the request.
Dan Lavu 2017-12-14 10:43:58 UTC Status ON_QA VERIFIED
Pasi Karkkainen 2018-01-24 20:17:34 UTC CC pasik
errata-xmlrpc 2018-04-10 04:24:54 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2018-04-10 17:09:10 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2018-04-10 13:09:10 UTC
errata-xmlrpc 2018-04-10 17:10:42 UTC Link ID Red Hat Product Errata RHEA-2018:0929
Pavel Březina 2020-05-02 18:35:05 UTC Link ID Github SSSD/sssd/issues/4298

Back to bug 1400614