SSSD / sssd

#2456 Error message not helpful if extdom lookup fails
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

When looking up a trusted user with an extop, we usually just print "Operations Error". We should give also a hint that the error is likely to be on the server side and that the admin should go and inspect the sssd server side logs and/or slapd logs.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.3

The scope of this ticket is trivial -- just add a better DEBUG message. A better fix is planned for a later version in ticket #2463.

Fields changed

owner: somebody => sbose
status: new => assigned
  • master: bc85b7e2b7b1569e64d8832c52cab9ad165e6fc1

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

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

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

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
None
None
None
High
defect
SSSD
1.12.1
0
0
0
0
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.