#1434 Typo in logging when ldap search base is not set
Closed: Fixed None Opened 11 years ago by kaushikub.

Change SSSd to SSSD in:

[ad_set_search_bases] (0x0100): Search base not set. SSSd will attempt to discover it later, when connecting to the LDAP server


Fields changed

keywords: => easyfix
priority: major => trivial

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0
rhbz: => 0

Fields changed

owner: somebody => mzidek
proposed_priority: => Undefined

0051296 fixed in master

resolution: => fixed
status: new => closed

Fields changed

patch: 0 => 1

Metadata Update from @kaushikub:
- 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/2476

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