#2435 SSSD connection terminated after failing anonymous bind to IBM Tivoli Directory Server
Closed: Fixed None Opened 6 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1139878

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
SSSD fails simple bind to the IBM Tivoli Directory Server that does not allow
anonymous binds because the connection is terminated upon the failure.

Version-Release number of selected component (if applicable):
# cat installed-rpms | grep sssd
sssd-1.9.2-129.el6_5.4.x86_64                               Fri Aug 15 15:40:45
2014
sssd-client-1.9.2-129.el6_5.4.x86_64                        Fri Aug 15 15:40:44
2014

How reproducible:
100% (customer's environment)

Steps to Reproduce:
1. IBM Directory Server not allowing anonymous binds
2. RH client that auths to the IBM dirsrv via SSSD
3.

Actual results:
Terminates the connection, thus failing the simple bind attempt.

Expected results:
Retain the connection, attempt simple bind after failing the anonymous bind
attempt.

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
owner: somebody => preichl
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.2

Fields changed

patch: 0 => 1

mark: => 0
resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.12.2

3 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/3477

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