blob: 90d797f7f17ea85da44d91e1ac786ee0e26a430c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
<refentry id="idmap_tdb.8">
<refmeta>
<refentrytitle>idmap_tdb</refentrytitle>
<manvolnum>8</manvolnum>
<refmiscinfo class="source">Samba</refmiscinfo>
<refmiscinfo class="manual">System Administration tools</refmiscinfo>
<refmiscinfo class="version">3.6</refmiscinfo>
</refmeta>
<refnamediv>
<refname>idmap_tdb</refname>
<refpurpose>Samba's idmap_tdb Backend for Winbind</refpurpose>
</refnamediv>
<refsynopsisdiv>
<title>DESCRIPTION</title>
<para>
The idmap_tdb plugin is the default backend used by winbindd
for storing SID/uid/gid mapping tables.
</para>
<para>
In contrast to read only backends like idmap_rid, it is an allocating
backend: This means that it needs to allocate new user and group IDs in
order to create new mappings. The allocator can be provided by the
idmap_tdb backend itself or by any other allocating backend like
idmap_ldap or idmap_tdb2. This is configured with the
parameter <parameter>idmap alloc backend</parameter>.
</para>
<para>
Note that in order for this (or any other allocating) backend to
function at all, the default backend needs to be writeable.
The ranges used for uid and gid allocation are the default ranges
configured by "idmap uid" and "idmap gid".
</para>
<para>
Furthermore, since there is only one global allocating backend
responsible for all domains using writeable idmap backends,
any explicitly configured domain with idmap backend tdb
should have the same range as the default range, since it needs
to use the global uid / gid allocator. See the example below.
</para>
</refsynopsisdiv>
<refsect1>
<title>IDMAP OPTIONS</title>
<variablelist>
<varlistentry>
<term>range = low - high</term>
<listitem><para>
Defines the available matching uid and gid range for which the
backend is authoritative.
If the parameter is absent, Winbind fails over to use
the "idmap uid" and "idmap gid" options
from smb.conf.
</para></listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>EXAMPLES</title>
<para>
This example shows how tdb is used as a the default idmap backend.
It configures the idmap range through the global options for all
domains encountered. This same range is used for uid/gid allocation.
</para>
<programlisting>
[global]
# "backend = tdb" is redundant here since it is the default
idmap config * : backend = tdb
idmap config * : range = 1000000-2000000
</programlisting>
<para>
This (rather theoretical) example shows how tdb can be used as the
allocating backend while ldap is the default backend used to store
the mappings.
It adds an explicit configuration for some domain DOM1, that
uses the tdb idmap backend. Note that the same range as the
default uid/gid range is used, since the allocator has to serve
both the default backend and the explicitly configured domain DOM1.
</para>
<programlisting>
[global]
idmap config * : backend = ldap
idmap config * : range = 1000000-2000000
# use a different uid/gid allocator:
idmap config DOM1 : backend = tdb
idmap config DOM1 : range = 1000000-2000000
</programlisting>
</refsect1>
<refsect1>
<title>AUTHOR</title>
<para>
The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.
</para>
</refsect1>
</refentry>
|
