My idea is to replace default "cifs_idmap_sss.so" plugin by "idmapwb.so" winbind plugin, in order to SSSD becomes a client of winbind. To avoid to change nsswitch.conf : passwd:???? files sss shadow:???? files sss group:????? files sss into passwd:???? files winbind shadow:???? files winbind group:????? files winbind because I need an other access in sftp, this is using default sssd. I tried mix copnfiguration like : passwd:???? files sss winbind? (or files winbind sss) shadow:???? files sss winbind (or files winbind sss) group:????? files sss winbind (or files winbind sss) which gave poor result, very slow access to the share especially when click on security tab on windows 7. Le 20/06/2019 ? 13:32, Rowland penny via samba a ?crit?:> On 20/06/2019 17:19, Edouard Guign? via samba wrote: >> Hello, >> >> I am reading RHEL 7 docs concerning samba integration, and I found >> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/windows_integration_guide/index#winbind >> >> >> "4.2.4. Switching Between SSSD and Winbind for SMB Share Access >> This procedure describes how you can switch between SSSD and Winbind >> plug-ins that are used for accessing SMB shares from SSSD clients. " >> >> Who is responsible for the developpement of the "Winbind plug-in" >> used for accessing SMB shares from SSSD clients ? >> Samba team or RHEL SSSD team ? >> >> Best Regards, >> >> Edouard >> >> > Bit lost here, it says you need cifs-utils for winbind to access SMB > shares, must be a different cifs-utils to the Debian one that is used > to mount shares. > > If it is an sssd plug-in, then it will be developed by Red-Hat. > > What are you trying to achieve ? > > Rowland > > >
On 20/06/2019 17:54, Edouard Guign? via samba wrote:> My idea is to replace default "cifs_idmap_sss.so" plugin by > "idmapwb.so" winbind plugin, in order to SSSD becomes a client of > winbind. > To avoid to change nsswitch.conf : > passwd:???? files sss > shadow:???? files sss > group:????? files sss > > into > > passwd:???? files winbind > shadow:???? files winbind > group:????? files winbind > > because I need an other access in sftp, this is using default sssd. > > I tried mix copnfiguration like : > passwd:???? files sss winbind? (or files winbind sss) > shadow:???? files sss winbind (or files winbind sss) > group:????? files sss winbind (or files winbind sss) > > which gave poor result, very slow access to the share especially when > click on security tab on windows 7. > > > Le 20/06/2019 ? 13:32, Rowland penny via samba a ?crit?: >> On 20/06/2019 17:19, Edouard Guign? via samba wrote: >>> Hello, >>> >>> I am reading RHEL 7 docs concerning samba integration, and I found >>> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/windows_integration_guide/index#winbind >>> >>> >>> "4.2.4. Switching Between SSSD and Winbind for SMB Share Access >>> This procedure describes how you can switch between SSSD and Winbind >>> plug-ins that are used for accessing SMB shares from SSSD clients. " >>> >>> Who is responsible for the developpement of the "Winbind plug-in" >>> used for accessing SMB shares from SSSD clients ? >>> Samba team or RHEL SSSD team ?Make sure smb.conf is set up correctly authconfig --enablekrb5 --enablewinbind --enablewinbindauth --enablemkhomedir --update Check that the passwd, group and shadow lines in /etc/nsswitch.conf look like this: passwd:???? files winbind group:????? files winbind shadow:?? files yum remove sssd* You should be good to go
This way is so easier... Thank you Rowland Le 20/06/2019 ? 14:01, Rowland penny via samba a ?crit?:> On 20/06/2019 17:54, Edouard Guign? via samba wrote: >> My idea is to replace default "cifs_idmap_sss.so" plugin by >> "idmapwb.so" winbind plugin, in order to SSSD becomes a client of >> winbind. >> To avoid to change nsswitch.conf : >> passwd:???? files sss >> shadow:???? files sss >> group:????? files sss >> >> into >> >> passwd:???? files winbind >> shadow:???? files winbind >> group:????? files winbind >> >> because I need an other access in sftp, this is using default sssd. >> >> I tried mix copnfiguration like : >> passwd:???? files sss winbind? (or files winbind sss) >> shadow:???? files sss winbind (or files winbind sss) >> group:????? files sss winbind (or files winbind sss) >> >> which gave poor result, very slow access to the share especially when >> click on security tab on windows 7. >> >> >> Le 20/06/2019 ? 13:32, Rowland penny via samba a ?crit?: >>> On 20/06/2019 17:19, Edouard Guign? via samba wrote: >>>> Hello, >>>> >>>> I am reading RHEL 7 docs concerning samba integration, and I found >>>> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html-single/windows_integration_guide/index#winbind >>>> >>>> >>>> "4.2.4. Switching Between SSSD and Winbind for SMB Share Access >>>> This procedure describes how you can switch between SSSD and >>>> Winbind plug-ins that are used for accessing SMB shares from SSSD >>>> clients. " >>>> >>>> Who is responsible for the developpement of the "Winbind plug-in" >>>> used for accessing SMB shares from SSSD clients ? >>>> Samba team or RHEL SSSD team ? > > Make sure smb.conf is set up correctly > > authconfig --enablekrb5 --enablewinbind --enablewinbindauth > --enablemkhomedir --update > > Check that the passwd, group and shadow lines in /etc/nsswitch.conf > look like this: > > passwd:???? files winbind > group:????? files winbind > > shadow:?? files > > yum remove sssd* > > You should be good to go > >