sous-chefs/samba

sssd-libwbclient is needed on RHEL/CentOS 7.5+ systems

Open

#88 opened on Aug 22, 2018

View on GitHub
 (5 comments) (5 reactions) (0 assignees)Ruby (54 forks)auto 404
BugGood First IssueHelp Wantedhacktoberfest

Repository metrics

Stars
 (30 stars)
PR merge metrics
 (PR metrics pending)

Description

Cookbook version

1.1.4

Chef-client version

14.2.0

Platform Details

RHEL 7.5 x86_64 samba-4.7.1-9.el7_5.x86_64

Scenario:

When a RHEL system is AD joined using SSSD, winbind does not function as samba is not AD joined. To get samba to work with an systems joined to the AD through SSSD the package sssd-libwbclient is needed. However, it can't just blindly be installed as it will override winbind, and for folks who join a system to the AD using samba, they rely on winbind.

An attribute or a flag of some sort is needed to state that SSSD is being used and as such the package sssd-libwbclient needs to be installed.

Steps to Reproduce:

Setup cookbook to configure a RHEL/CentOS 7.5 system that is joined to the AD via SSSD to run as a file share (security = ads) startup of samba will fail because winbind is not enabled, obscure error message in /var/log/samba/log.smbd: [2018/08/22 10:48:42.481282, 0] ../source3/auth/auth_util.c:1399(make_new_session_info_guest) create_local_token failed: NT_STATUS_NO_MEMORY [2018/08/22 10:48:42.482097, 0] ../source3/smbd/server.c:2011(main) ERROR: failed to setup guest info.

Winbind will not start due to not being AD joined, solution is to install the sssd-libwbclient package.

Expected Result:

Samba to start and serve shares.

Actual Result:

Already mentioned in steps to reproduce.

Contributor guide