On Mon, 2016-09-12 at 09:41 +0200, Sumit Bose wrote:
> On Fri, Sep 09, 2016 at 07:07:58PM +0000, Joakim Tjernlund wrote:
> >
> > On Fri, 2016-09-09 at 20:53 +0200, Lukas Slebodnik wrote:
> > >
> > > On (09/09/16 18:35), Joakim Tjernlund wrote:
> > > >
> > > >
> > > > On Fri, 2016-09-09 at 19:40 +0200, Lukas Slebodnik wrote:
> > > > >
> > > > >
> > > > > On (09/09/16 16:25), Sumit Bose wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Sep 09, 2016 at 02:00:53PM +0000, Joakim Tjernlund
wrote:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Fri, 2016-09-09 at 14:48 +0200, Sumit Bose wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Sep 09, 2016 at 11:46:27AM +0000, Joakim
Tjernlund wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Trying to bring up samba with sssd-13.4 and
for some reason samba fails
> > > > > > > > > to lookup users: From smb.log I have:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On older systems I have samba 3.6.25 and sssd
1.12.5 and there samba works fine.
> > > > > > > > > Is there som change I have missed when
upgrading to newer samba sssd?
> > > > > > > >
> > > > > > > > Are you using SSSD's version of libwbclient to
help samba to map SID to
> > > > > > >
> > > > > > > hmm, I got both (/usr/lib64/libwbclient.so.0 and
/usr/lib64/sssd/modules/libwbclient.so)
> > > > > > > and wbinfo -n 'TRAN_01\jocke' reports:
> > > > > > > wbinfo -n 'TRAN_01\jocke'
> > > > > > > could not obtain winbind interface details:
WBC_ERR_WINBIND_NOT_AVAILABLE
> > > > > > > could not obtain winbind separator!
> > > > > > > failed to call wbcLookupName:
WBC_ERR_WINBIND_NOT_AVAILABLE
> > > > > > > Could not lookup name TRAN_01\jocke
> > > > > > >
> > > > > > > I guess the problem is that samba uses its own
libwbclient.so and winbind
> > > > > > > is not configured?
> > > > > >
> > > > > > iirc you are using gentoo. In Fedora/RHEL is is possible to
switch
> > > > > > those two libraries with the alternatives command.
> > > > > >
> > > > > > To make at least wbinfo try to use SSSD's version you
can try calling it
> > > > > > as:
> > > > > >
> > > > > > LD_LIBRARY_PATH=/usr/lib64/sssd/modules wbinfo -n
'TRAN_01\jocke'
> > > > > >
> > > > > > as long as wbinfo is not complied with rpath or similar it
should pick
> > > > > > /usr/lib64/sssd/modules/libwbclient.so.0 instead of
> > > > > > /usr/lib64/libwbclient.so.0. If there is no
> > > > > > /usr/lib64/sssd/modules/libwbclient.so.0 you should add it
as a softlink
> > > > > > to /usr/lib64/sssd/modules/libwbclient.so. I would also
expect that
> > > > > > there are link with ends with a version number like 11 or
12.
> > > > > >
> > > > > and samba 4.5 has libwbclient.so.0.13
> > > > >
> > > > > [root@host ~]# rpm -qf
/usr/lib64/samba/wbclient/libwbclient.so.0.13
> > > > > libwbclient-4.5.0-0.0.rc1.fc26.x86_64
> > > > and lives in its own package. Is this new from samba >= 4.5 ?
> > > >
> > > Yes,
> > > I cannot see it in official announcement (2 days old :-)
> > >
https://lists.samba.org/archive/samba-technical/2016-September/116033.html
> > > but samba 4.4.5 has just a libwbclient.so.0.12
> > >
> > > But if you asked about packaging then
> > > the libwbclient (from samba) and sssd-libwbclient are separate packages
> > > on fedora since I remember :-)
> > >
> >
> > I see, now the 1000 $ question, is sssd able to use libwbclient from samba too?
>
> It does not have to. libwbclient is an interface for Samba components to
> get data from winbind. The SSSD version of libwbclient implements some
> parts to the interface to allow the Samba components to get SID, name,
> POSIX ID mapping data from SSSD instead of winbind. So SSSD provides the
> interface but does not use it.
>
I guess that would be somewhat unusual case and not really needed.
To summarize, in Fedora, the libwbclient libs from samba resp. sssd are installed
under non standard search paths, are separate pkgs and there is a
"script"(alternatives)
that selects between the two by creating a symlink in /usr/lib{,64,32} to either
samba's libwbclient or sssd's libwbclient. Is that correct?
Have you considered a more direct way? That is, if sssd's libwbclient is
built/installed
it always takes over(eliminaiting the need for an alternatives script? Or just require
that only one of libwbclient pkgs can be installed at the same time?
sssd-libwbclient does not implement all functions. That's reason why it is not
a default; and just an alternative.
Is there a configure option to sssd which builds libwbclient or is it
always built?
Yes, it is.
--with-libwbclient Whether to build SSSD implementation of libwbclient
[yes]
And as you can see default is yes.
LS