#2281 [GSS 7.0] if access_provider is not set sssd fails with no good error
Closed: Fixed Opened by dpal.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1075141

Description of problem:
Apparently its critical that "id_provider" and "access_provider" be "ad".  If
access_provider is ldap, sssd falls over hard without any good error.  If both
are set to "ad", things seem to work correctly and Sites is consulted.
Version-Release number of selected component (if applicable):
How reproducible:
Configure sssd to talk to AD server.
Set id_provider=ad but leave access_provider set to something else.
Actual results:
sssd falls over hard without a good error message
Expected results:
Have sssd indicate via error message that there are inconsistencies with
"id_provider" and "access_provider"
Additional info:
https://fedorahosted.org/sssd/wiki/Configuring_sssd_with_ad_server
http://jhrozek.livejournal.com/#post-jhrozek-2801
http://jhrozek.livejournal.com/#post-jhrozek-3019

This is just a man page change.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.12 beta
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: SSSD 1.12 beta => SSSD 1.12 beta 2

Fields changed

owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned

Patch is available and acked, but we're past the string freeze. Moving to 1.12.1

milestone: SSSD 1.12 beta 2 => SSSD 1.12.1

  • master: b3f56d9e4bd065590383eb1f812a3b77e3c56f24

resolution: => fixed
status: assigned => closed

Metadata Update from @dpal:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.12.1

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

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.

Metadata