#1257 Unable to bind to IPA server when minssf set
Closed: Fixed None Opened 8 years ago by sgallagh.

https://bugzilla.redhat.com/show_bug.cgi?id=803436 (Fedora)

Description of problem:
I changed the configuration of my IPA server and set minssf to 56, as is
documented n the IPA guide. All my RHEL based systems continue to function. But
my one fedora desktop is now unable to bind to the server, and as such is not
getting any updated information.

From the logs:
Unexpected result from ldap: Server is unwilling to perform(53), Minimum SSF
not met.

Version-Release number of selected component (if applicable):

How reproducible:
set minssf on server, watch sssd fail to bind. Frankly with all the caching
that goes on I wouldn't have even noticed that it wasn't working except for a
password change that arose after minssf was set.

As I said this continues to work fine in RHEL 5 and 6, so chances are this is
something new or a bugfix that wasn't forward ported.


Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
owner: somebody => sgallagh
patch: 0 => 1
status: new => assigned
tests: => 0
testsupdated: => 0
upgrade: => 0

Fixed by:
- f651436 (master)
- f28ab6e (sssd-1-8)

resolution: => fixed
status: assigned => closed

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.8.2 (LTM)

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

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.