| 1 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>idmap_tdb2</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="idmap_tdb2"><a name="idmap_tdb2.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>idmap_tdb2 — Samba's idmap_tdb2 Backend for Winbind</p></div><div class="refsynopsisdiv" title="DESCRIPTION"><h2>DESCRIPTION</h2><p>
|
|---|
| 2 | The idmap_tdb2 plugin is a substitute for the default idmap_tdb
|
|---|
| 3 | backend used by winbindd for storing SID/uid/gid mapping tables
|
|---|
| 4 | in clustered environments with Samba and CTDB.
|
|---|
| 5 | </p><p>
|
|---|
| 6 | In contrast to read only backends like idmap_rid, it is an allocating
|
|---|
| 7 | backend: This means that it needs to allocate new user and group IDs in
|
|---|
| 8 | order to create new mappings.
|
|---|
| 9 | </p></div><div class="refsect1" title="IDMAP OPTIONS"><a name="id266343"></a><h2>IDMAP OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">range = low - high</span></dt><dd><p>
|
|---|
| 10 | Defines the available matching uid and gid range for which the
|
|---|
| 11 | backend is authoritative.
|
|---|
| 12 | </p></dd><dt><span class="term">script</span></dt><dd><p>
|
|---|
| 13 | This option can be used to configure an external program
|
|---|
| 14 | for performing id mappings instead of using the tdb
|
|---|
| 15 | counter. The mappings are then stored int tdb2 idmap
|
|---|
| 16 | database. For details see the section on IDMAP SCRIPT below.
|
|---|
| 17 | </p></dd></dl></div></div><div class="refsect1" title="IDMAP SCRIPT"><a name="id266833"></a><h2>IDMAP SCRIPT</h2><p>
|
|---|
| 18 | The tdb2 idmap backend supports an external program for performing id mappings
|
|---|
| 19 | through the smb.conf option <em class="parameter"><code>idmap config * : script</code></em> or
|
|---|
| 20 | its deprecated legacy form <em class="parameter"><code>idmap : script</code></em>.
|
|---|
| 21 | </p><p>
|
|---|
| 22 | The mappings obtained by the script are then stored in the idmap tdb2
|
|---|
| 23 | database instead of mappings created by the incrementing id counters.
|
|---|
| 24 | It is therefore important that the script covers the complete range of
|
|---|
| 25 | SIDs that can be passed in for SID to Unix ID mapping, since otherwise
|
|---|
| 26 | SIDs unmapped by the script might get mapped to IDs that had
|
|---|
| 27 | previously been mapped by the script.
|
|---|
| 28 | </p><p>
|
|---|
| 29 | The script should accept the following command line options.
|
|---|
| 30 | </p><pre class="programlisting">
|
|---|
| 31 | SIDTOID S-1-xxxx
|
|---|
| 32 | IDTOSID UID xxxx
|
|---|
| 33 | IDTOSID GID xxxx
|
|---|
| 34 | </pre><p>
|
|---|
| 35 | And it should return one of the following responses as a single line of
|
|---|
| 36 | text.
|
|---|
| 37 | </p><pre class="programlisting">
|
|---|
| 38 | UID:yyyy
|
|---|
| 39 | GID:yyyy
|
|---|
| 40 | SID:yyyy
|
|---|
| 41 | ERR:yyyy
|
|---|
| 42 | </pre></div><div class="refsect1" title="EXAMPLES"><a name="id266880"></a><h2>EXAMPLES</h2><p>
|
|---|
| 43 | This example shows how tdb2 is used as a the default idmap backend.
|
|---|
| 44 | </p><pre class="programlisting">
|
|---|
| 45 | [global]
|
|---|
| 46 | idmap config * : backend = tdb2
|
|---|
| 47 | idmap config * : range = 1000000-2000000
|
|---|
| 48 | </pre><p>
|
|---|
| 49 | This example shows how tdb2 is used as a the default idmap backend
|
|---|
| 50 | using an external program via the script parameter:
|
|---|
| 51 | </p><pre class="programlisting">
|
|---|
| 52 | [global]
|
|---|
| 53 | idmap config * : backend = tdb2
|
|---|
| 54 | idmap config * : range = 1000000-2000000
|
|---|
| 55 | idmap config * : script = /usr/local/samba/bin/idmap_script.sh
|
|---|
| 56 | </pre></div><div class="refsect1" title="AUTHOR"><a name="id265703"></a><h2>AUTHOR</h2><p>
|
|---|
| 57 | The original Samba software and related utilities
|
|---|
| 58 | were created by Andrew Tridgell. Samba is now developed
|
|---|
| 59 | by the Samba Team as an Open Source project similar
|
|---|
| 60 | to the way the Linux kernel is developed.
|
|---|
| 61 | </p></div></div></body></html>
|
|---|