Learn more about these different git repos.
Other Git URLs
In case sssd is set with id_provider=proxy and auth_provider=ldap and at the same time ldaps:// (not TLS) is used, then our connection mechanism does not work well. The caller then must set sdap_sh_connected which we don't do. Everything works well with TLS.
This is an example of why we must refactor the LDAP connection logic completely, the caller should not be responsible for setting a flag himself.
owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned
summary: id_provider=files with auth_provider=ldap does not work reliably => id_provider=proxy with auth_provider=ldap does not work reliably
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1209483 (Red Hat Enterprise Linux 7)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1209483 1209483]
milestone: NEEDS_TRIAGE => SSSD 1.13 alpha
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.13 alpha
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:
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.
to comment on this ticket.