[PATCH] docs-xml/winbindnssinfo: clarify interaction with idmap_ad etc.
rpenny at samba.org
Tue Jan 7 14:25:47 UTC 2020
On 07/01/2020 12:18, Björn JACKE wrote:
> On 2020-01-07 at 10:30 +0000 Rowland penny via samba-technical sent off:
>> Domain Controller supports the Microsoft "Services for Unix" (SFU)
>> instead of:
>> Domain Controller does support the Microsoft "Services for Unix" (SFU)
> I'm always happy to improve my English grammar skills, can you say why
> "supports" is wrong here or is this just a matter of taste here?
I would never say 'does support' in this context:
your Active Directory Domain Controller does support the Microsoft
"Services for Unix" (SFU) LDAP schema.
I would say:
your Active Directory Domain Controller supports the Microsoft "Services
for Unix" (SFU) LDAP schema.
It is just the way that we English speak ;-)
>> Make sure to consult the documentation of the idmap backend that you are
>> As it only works with idmap_ad, wouldn't it be better as:
>> Make sure to consult the documentation for the idmap_ad backend.
> honestly I'm not entirely sure that no other idmap module can work with this
> parameter also, for example idmap rfc2307. Actually if no idmap module is left
> that supports this setting of winbind nss info, then the only parameter left
> for this would be "template" and then we should actually remove this parameter
> entirely. There might however also be third-party idmap modules, which make use
> of this setting of "winbind nss info" and this is why I carefully chose the
> words this way (for now).
As far as I am aware, idmap_rfc2307 only uses the uidNumber & gidNumber
attributes, so, like 'rid' & 'autorid', it only uses 'template'. If
there is a third party idmap module, Samba knows nothing about it, so
shouldn't even be considered.
Unless the idmap_ad module is removed, winbind nss info is needed and if
used in smb.conf, we should point users to the relevant documentation,
which in this case is 'man idmap_ad'.
More information about the samba-technical