#489 GSSAPI and START_TLS should be mutually-exclusive
Closed: Duplicate None Opened 13 years ago by sgallagh.

When using GSSAPI-encrypted LDAP communications, we should disable (silently?) ldap_id_use_start_tls, as it is unnecessary overhead for no additional gain.


We should disable and warn about the duplication.

milestone: NEEDS_TRIAGE => SSSD 1.4.0

Fields changed

milestone: SSSD 1.5.0 => SSSD 1.6.0

Fields changed

coverity: =>
description: When using GSSAPI-encrypted LDAP communications, we should disable (silently?) ldap_id_use_start_tls, as it is unneccessary overhead for no additional gain. => When using GSSAPI-encrypted LDAP communications, we should disable (silently?) ldap_id_use_start_tls, as it is unnecessary overhead for no additional gain.
milestone: SSSD 1.6.0 => SSSD Deferred
upgrade: => 0

Fields changed

rhbz: => 0

Now that we consider supporting SASL/EXTERNAL it might make sense to better inspect colliding configurations.

blockedby: =>
blocking: =>
feature_milestone: =>
patch: => 0
proposed_priority: => Important

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: SSSD Deferred => SSSD 1.10 beta

Fields changed

priority: minor => major

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Fields changed

mark: => 0

Hasn't been needed for 5 years..

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => minor
review: => 1

The issue is much better described in ticket #2536, so I'll mark this one as a duplicate. Sorry for the spam.

resolution: => duplicate
status: new => closed

Mass-moving tickets not planned for the next two releases.

Please reply with a comment if you disagree about the move..

milestone: SSSD 1.13 backlog => SSSD 1.15 beta

Metadata Update from @sgallagh:
- Issue set to the milestone: SSSD Future releases (no date set yet)

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

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