Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
SSSD service should fail to start when an invalid section is added.
For example, when a secrets section is added to test secrets service. The sssd.log clearly shows error: "Section [secrets] is not allowed. Check for typos."
Version-Release number of selected component (if applicable):
sssd-1.14.0-43.el7
How reproducible:
Always
Steps to Reproduce:
1. Edit sssd.conf file and add a secrets section as given below:
[secrets]
debug_level = 0xFFF0
provider = local
2. Restart sssd service
3. Verify error log in sssd.log file
Actual results:
SSSD service successfully starts.
Expected results:
SSSD service should fail to start or show warning on the service status.
Additional info:
I don't think we should fail to start. We should fail to start if you add secrets to the "services" line, but not if a section is created.
Try creating a totally bogus section..
Actually, the [services] section is /required/ in many setups like if you want to set up proxying to custodia or even enable debugging.
This is not a bug.
(In reply to Pavel Březina from comment #4)
> And isn't it a bug in config check that it assumes secrets to be invalid?
Yeah, that's possible, Fabiano already has a PR open on github that addresses this..
The sssd.log shows "Section [secrets] is not allowed. Check for typos." So i assumed that a secrets section is invalid.
Also, I logged this bug to address Jakub's response on one of the SSSD secrets test case, sent for review:
----------------------------------------------------------------------------------------
*Case-03: Test sssd behaviour by adding a secrets section*
Steps:
- Edit sssd.conf file and add a secrets section as given below:
[secrets]
debug_level = 0xFFF0
provider = local
- Restart sssd service
- Verify error log in sssd.log file
Result seen: SSSD service successfully restarts. Logged message in sssd.log:
"Section [secrets] is not allowed. Check for typos."
--------------------------------------------------------------------------------------------
Jakub's response: This is a known bug, you can log it if you like.
Description of problem: SSSD service should fail to start when an invalid section is added. For example, when a secrets section is added to test secrets service. The sssd.log clearly shows error: "Section [secrets] is not allowed. Check for typos." Version-Release number of selected component (if applicable): sssd-1.14.0-43.el7 How reproducible: Always Steps to Reproduce: 1. Edit sssd.conf file and add a secrets section as given below: [secrets] debug_level = 0xFFF0 provider = local 2. Restart sssd service 3. Verify error log in sssd.log file Actual results: SSSD service successfully starts. Expected results: SSSD service should fail to start or show warning on the service status. Additional info: