#1347 protocol fallback when resolving SRV queries does not work properly
Closed: Invalid None Opened 11 years ago by jhrozek.

Currently the SSSD tries to search for one "preferred" protocol (tcp in case of LDAP and udp in case of Kerberos) and in case the query is not successful, falls back to the other protocol. However, after the SRV query expires, we only seem to search the preferred protocol.

Possibly the expiry code is buggy.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0
priority: major => minor

Fields changed

owner: somebody => mzidek
proposed_priority: => Undefined

I've tested this and protocol fallback worked fine. I've changed the expiration time to 10 seconds and manually disabled TCP/UDP ports on server side (after one successful transaction with that server) to see how SSSD behaves when working server expires and is no longer available. Protocol fallback always worked (SSSD tried srv resolution with both protocols). Closing the ticket as worksforme.

resolution: => worksforme
status: new => closed

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

7 years ago

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/2389

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.

Login to comment on this ticket.

Metadata