1IDMAP_AD(8)               System Administration tools              IDMAP_AD(8)
2
3
4

NAME

6       idmap_ad - Samba's idmap_ad Backend for Winbind
7

DESCRIPTION

9       The idmap_ad plugin provides a way for Winbind to read id mappings from
10       an AD server that uses RFC2307/SFU schema extensions. This module
11       implements only the "idmap" API, and is READONLY. Mappings must be
12       provided in advance by the administrator by adding the uidNumber
13       attributes for users and gidNumber attributes for groups in the AD.
14       Winbind will only map users that have a uidNumber and whose primary
15       group have a gidNumber attribute set. It is however recommended that
16       all groups in use have gidNumber attributes assigned, otherwise they
17       are not working.
18
19       Currently, the ad backend does not work as the default idmap backend,
20       but one has to configure it separately for each domain for which one
21       wants to use it, using disjoint ranges. One usually needs to configure
22       a writeable default idmap range, using for example the tdb or ldap
23       backend, in order to be able to map the BUILTIN sids and possibly other
24       trusted domains. The writeable default config is also needed in order
25       to be able to create group mappings. This catch-all default idmap
26       configuration should have a range that is disjoint from any explicitly
27       configured domain with idmap backend ad. See the example below.
28

IDMAP OPTIONS

30       range = low - high
31           Defines the available matching UID and GID range for which the
32           backend is authoritative. Note that the range acts as a filter. If
33           specified any UID or GID stored in AD that fall outside the range
34           is ignored and the corresponding map is discarded. It is intended
35           as a way to avoid accidental UID/GID overlaps between local and
36           remotely defined IDs.
37
38       schema_mode = <rfc2307 | sfu | sfu20>
39           Defines the schema that idmap_ad should use when querying Active
40           Directory regarding user and group information. This can be either
41           the RFC2307 schema support included in Windows 2003 R2 or the
42           Service for Unix (SFU) schema. For SFU 3.0 or 3.5 please choose
43           "sfu", for SFU 2.0 please choose "sfu20". Please note that the
44           behavior of primary group membership is controlled by the
45           unix_primary_group option.
46
47       unix_primary_group = yes/no
48           Defines whether the user's primary group is fetched from the SFU
49           attributes or the AD primary group. If set to yes the primary group
50           membership is fetched from the LDAP attributes (gidNumber). If set
51           to no the primary group membership is calculated via the
52           "primaryGroupID" LDAP attribute.
53
54           Default: no
55
56       unix_nss_info = yes/no
57           If set to yes winbind will retrieve the login shell and home
58           directory from the LDAP attributes. If set to no the or the AD LDAP
59           entry lacks the SFU attributes the options template shell and
60           template homedir are used.
61
62           Default: no
63

EXAMPLES

65       The following example shows how to retrieve idmappings from our
66       principal and trusted AD domains. If trusted domains are present id
67       conflicts must be resolved beforehand, there is no guarantee on the
68       order conflicting mappings would be resolved at this point. This
69       example also shows how to leave a small non conflicting range for local
70       id allocation that may be used in internal backends like BUILTIN.
71
72                [global]
73                workgroup = CORP
74
75                idmap config * : backend = tdb
76                idmap config * : range = 1000000-1999999
77
78                idmap config CORP : backend  = ad
79                idmap config CORP : range = 1000-999999
80
81

AUTHOR

83       The original Samba software and related utilities were created by
84       Andrew Tridgell. Samba is now developed by the Samba Team as an Open
85       Source project similar to the way the Linux kernel is developed.
86
87
88
89Samba 4.9.1                       05/11/2019                       IDMAP_AD(8)
Impressum