On Sat, 2013-01-26 at 12:46 +, Rob McCorkell wrote:
If you provision/run with idmap_ldb:use rfc2307 then you can assign each
user/group a uidNumber/gidNumber which then is/can be obeyed by samba/nslcd.
Sorry, I should have made myself more clear. Our current setup uses
the nslcd
If you provision/run with idmap_ldb:use rfc2307 then you can assign each
user/group a uidNumber/gidNumber which then is/can be obeyed by samba/nslcd.
Sorry, I should have made myself more clear. Our current setup uses the nslcd
approach to get the UIDs and GIDs as mapped from the RID of each
On 01/25/2013 11:43 AM, Rob McCorkell wrote:
Samba3 allowed for the setting of idmaps and passdb backends to
configure how users were pulled in. This made integrating with
existing LDAP databases, other other forms of authentication easy,
since Samba could be configured to present the same UID
Thanks for the explanation - I wasn't thinking too much about multiple
domains, and I guess it would be an issue. A potential solution would be
to have offsets for each domain, specified in smb.conf? If I didn't have
too much on my plate already I would have a look at the mapping code and
On 01/26/2013 12:49 PM, Rob McCorkell wrote:
Thanks for the explanation - I wasn't thinking too much about multiple
domains, and I guess it would be an issue. A potential solution would
be to have offsets for each domain, specified in smb.conf? If I didn't
have too much on my plate already I
Samba3 allowed for the setting of idmaps and passdb backends to
configure how users were pulled in. This made integrating with existing
LDAP databases, other other forms of authentication easy, since Samba
could be configured to present the same UID and GID as directly from the
[insert other
2013-01-25 20:43 keltezéssel, Rob McCorkell írta:
Samba3 allowed for the setting of idmaps and passdb backends to
configure how users were pulled in. This made integrating with
existing LDAP databases, other other forms of authentication easy,
since Samba could be configured to present the
