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:
The "--updateall" parameter of authconfig doesn't update /etc/samba/smb.conf file but "--update" *does* update smb.conf.
Version-Release number of selected component (if applicable):
Name : authconfig Relocations: (not relocatable)
Version : 6.1.12 Vendor: Red Hat, Inc.
Release : 23.el6 Build Date: Wed 25 Feb 2015 04:35:09 AM EST
How reproducible:
Check the value of "security = " in /etc/samba/smb.conf:
[root@example bschonec]# grep security /etc/samba/smb.conf | egrep -v '^;|^#'
security = user
[root@example bschonec]#
# The current value is "user" (value doesn't matter in this context, we just need to note the value).
# Change the value:
[root@example bschonec]# authconfig --smbsecurity=ads --update
Starting nslcd: [ OK ]
[root@example bschonec]# grep security /etc/samba/smb.conf | egrep -v '^;|^#'
security = ads
# You can see that security has been updated to 'ads'.
# Now set it back to 'user' just to show that '--update' is working.
[root@example bschonec]# authconfig --smbsecurity=user --update
Starting nslcd: [ OK ]
[root@example bschonec]# grep security /etc/samba/smb.conf | egrep -v '^;|^#'
security = user
# You can see that security as been updated to 'user'.
# Now use the '--updateall'
[root@example bschonec]# authconfig --smbsecurity=ads --updateall
Starting oddjobd: [ OK ]
^[[AStarting nslcd: [ OK ]
[root@example bschonec]# grep security /etc/samba/smb.conf | egrep -v '^;|^#'
security = user
# You can see that security was NOT updated with the '--updateall'.
# Authconfig didn't change smb.conf at all.
Actual results:
security = <value> not updated. smb.conf file not modified with '--updateall' option.
Expected results:
security = <value> should be updated in smb.conf when envoking '--updateall' parameter of authconfig.
Additional info:
It makes sense to me that you SHOULD be able to change the values of the parameters even if you don't intend to use those parameters. Case in point: I use Puppet to manage the authconfig settings on my servers. I don't use SMB or SSSD but I do need to set them to a known value so that my servers pass audits (PCI, HIPAA, etc.). It would make sense that you can't/shouldn't change values if you don't intend to use SSSD/Winbind but enabling something (in my case, something that will break authorization completely) and then disabling it right away just to set the values seems counterintuitive -- especially since --update works and --updateall doesn't.
Yes, I could use '--update' in my puppet module but that would break backwards compatibility for everyone in the Puppet community that uses the modules (https://github.com/bschonec/puppet-authconfig.git).
--- Additional comment from Brian Schonecker on 2016-04-05 22:01:19 CEST ---
Edit: It would make sense that you CAN/SHOULD be able to change values....