RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
It is allowed to set non-numeric values to force_timeout parameter in sssd.conf. 

Version-Release number of selected component (if applicable):
sssd-1.9.2-7.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Set force_timeout = TRUE in DOMAIN Section of sssd.conf file
2. Restart sssd service.
3. Send SIGSTOP to process sssd_be
   # kill -s SIGSTOP <PID>

4. Monitor sssd.log file for the messages.
   # tail -f /var/log/sssd.log

Actual results:
The sssd service restarts successfully and sssd_be gets killed in 60 secs. Results are similar to the "force_timeout" default behaviour. 

Expected results:
An error should be shown while starting or restarting the sssd service. Non-numeric values shouldn't be allowed while setting force_timeout parameter in sssd.conf.

Upstream ticket:
https://fedorahosted.org/sssd/ticket/1621

Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.