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

NAME

6       idmap_tdb - Samba´s idmap_tdb Backend for Winbind
7

DESCRIPTION

9       The idmap_tdb plugin is the default backend used by winbindd for
10       storing SID/uid/gid mapping tables.
11
12       In contrast to read only backends like idmap_rid, it is an allocating
13       backend: This means that it needs to allocate new user and group IDs in
14       order to create new mappings. The allocator can be provided by the
15       idmap_tdb backend itself or by any other allocating backend like
16       idmap_ldap or idmap_tdb2. This is configured with the parameter idmap
17       alloc backend.
18
19       Note that in order for this (or any other allocating) backend to
20       function at all, the default backend needs to be writeable. The ranges
21       used for uid and gid allocation are the default ranges configured by
22       "idmap uid" and "idmap gid".
23
24       Furthermore, since there is only one global allocating backend
25       responsible for all domains using writeable idmap backends, any
26       explicitly configured domain with idmap backend tdb should have the
27       same range as the default range, since it needs to use the global uid /
28       gid allocator. See the example below.
29

IDMAP OPTIONS

31       range = low - high
32           Defines the available matching uid and gid range for which the
33           backend is authoritative. If the parameter is absent, Winbind fails
34           over to use the "idmap uid" and "idmap gid" options from smb.conf.
35

EXAMPLES

37       This example shows how tdb is used as a the default idmap backend. It
38       configures the idmap range through the global options for all domains
39       encountered. This same range is used for uid/gid allocation.
40
41                [global]
42                # "idmap backend = tdb" is redundant here since it is the default
43                idmap backend = tdb
44                idmap uid = 1000000-2000000
45                idmap gid = 1000000-2000000
46
47
48       This (rather theoretical) example shows how tdb can be used as the
49       allocating backend while ldap is the default backend used to store the
50       mappings. It adds an explicit configuration for some domain DOM1, that
51       uses the tdb idmap backend. Note that the same range as the default
52       uid/gid range is used, since the allocator has to serve both the
53       default backend and the explicitly configured domain DOM1.
54
55                [global]
56                idmap backend = ldap
57                idmap uid = 1000000-2000000
58                idmap gid = 1000000-2000000
59                # use a different uid/gid allocator:
60                idmap alloc backend = tdb
61
62                idmap config DOM1 : backend = tdb
63                idmap config DOM1 : range = 1000000-2000000
64
65

AUTHOR

67       The original Samba software and related utilities were created by
68       Andrew Tridgell. Samba is now developed by the Samba Team as an Open
69       Source project similar to the way the Linux kernel is developed.
70
71
72
73Samba 3.5                         08/02/2011                      IDMAP_TDB(8)
Impressum