#1635 investigate the behaviour of ldap_sasl_authid in 1.9.x
Closed: Fixed None Opened 10 years ago by jhrozek.

One of our users noted on the sssd-users list that the behaviour of ldap_sasl_authid has changed between 1.8 and 1.9:

We should investigate if it's the case and either amend the code or the docs as appropriate.

This is only true with AD and IPA providers, but yeah, we've regressed.

owner: somebody => jhrozek
status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.3
patch: 0 => 1

Fixed in master:
- 24c3186
- 459f70d
- e0d8619
- 73291a9
and sssd-1-9:
- b0e32fb
- 83e75fc
- 9f4df8c
- 2387cce

resolution: => fixed
status: assigned => closed

Fields changed

milestone: SSSD 1.9.3 => NEEDS_TRIAGE
resolution: fixed =>
status: closed => reopened

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.4

Fields changed

patch: 1 => 0

Sumit is looking into the second issue.

owner: jhrozek => sbose
status: reopened => new

New patch on the list

patch: 0 => 1

Two additional fixes landed in master:
- f2999e1
- 4ee7f39
and sssd-1-9:
- 163d021
- cbc1548

resolution: => fixed
status: new => closed

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

5 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/2677

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.