| 1 | <?xml version="1.0" encoding="iso-8859-1"?>
|
|---|
| 2 | <!DOCTYPE refentry PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
|
|---|
| 3 | <refentry id="idmap_ad.8">
|
|---|
| 4 |
|
|---|
| 5 | <refmeta>
|
|---|
| 6 | <refentrytitle>idmap_ad</refentrytitle>
|
|---|
| 7 | <manvolnum>8</manvolnum>
|
|---|
| 8 | <refmiscinfo class="source">Samba</refmiscinfo>
|
|---|
| 9 | <refmiscinfo class="manual">System Administration tools</refmiscinfo>
|
|---|
| 10 | <refmiscinfo class="version">3.6</refmiscinfo>
|
|---|
| 11 | </refmeta>
|
|---|
| 12 |
|
|---|
| 13 |
|
|---|
| 14 | <refnamediv>
|
|---|
| 15 | <refname>idmap_ad</refname>
|
|---|
| 16 | <refpurpose>Samba's idmap_ad Backend for Winbind</refpurpose>
|
|---|
| 17 | </refnamediv>
|
|---|
| 18 |
|
|---|
| 19 | <refsynopsisdiv>
|
|---|
| 20 | <title>DESCRIPTION</title>
|
|---|
| 21 | <para>The idmap_ad plugin provides a way for Winbind to read
|
|---|
| 22 | id mappings from an AD server that uses RFC2307/SFU schema
|
|---|
| 23 | extensions. This module implements only the "idmap"
|
|---|
| 24 | API, and is READONLY. Mappings must be provided in advance
|
|---|
| 25 | by the administrator by adding the uidNumber attributes for
|
|---|
| 26 | users and gidNumber attributes for groups in the AD. Winbind
|
|---|
| 27 | will only map users that have a uidNumber and whose primary
|
|---|
| 28 | group have a gidNumber attribute set. It is however
|
|---|
| 29 | recommended that all groups in use have gidNumber attributes
|
|---|
| 30 | assigned, otherwise they are not working.</para>
|
|---|
| 31 |
|
|---|
| 32 | <para>
|
|---|
| 33 | Note that the idmap_ad module has changed considerably since
|
|---|
| 34 | Samba versions 3.0 and 3.2.
|
|---|
| 35 | Currently, the <parameter>ad</parameter> backend
|
|---|
| 36 | does not work as the the default idmap backend, but one has
|
|---|
| 37 | to configure it separately for each domain for which one wants
|
|---|
| 38 | to use it, using disjoint ranges. One usually needs to configure
|
|---|
| 39 | a writeable default idmap range, using for example the
|
|---|
| 40 | <parameter>tdb</parameter> or <parameter>ldap</parameter>
|
|---|
| 41 | backend, in order to be able to map the BUILTIN sids and
|
|---|
| 42 | possibly other trusted domains. The writeable default config
|
|---|
| 43 | is also needed in order to be able to create group mappings.
|
|---|
| 44 | This catch-all default idmap configuration should have a range
|
|---|
| 45 | that is disjoint from any explicitly configured domain with
|
|---|
| 46 | idmap backend <parameter>ad</parameter>. See the example below.
|
|---|
| 47 | </para>
|
|---|
| 48 | </refsynopsisdiv>
|
|---|
| 49 |
|
|---|
| 50 | <refsect1>
|
|---|
| 51 | <title>IDMAP OPTIONS</title>
|
|---|
| 52 |
|
|---|
| 53 | <variablelist>
|
|---|
| 54 | <varlistentry>
|
|---|
| 55 | <term>range = low - high</term>
|
|---|
| 56 | <listitem><para>
|
|---|
| 57 | Defines the available matching UID and GID range for which the
|
|---|
| 58 | backend is authoritative. Note that the range acts as a filter.
|
|---|
| 59 | If specified any UID or GID stored in AD that fall outside the
|
|---|
| 60 | range is ignored and the corresponding map is discarded.
|
|---|
| 61 | It is intended as a way to avoid accidental UID/GID overlaps
|
|---|
| 62 | between local and remotely defined IDs.
|
|---|
| 63 | </para></listitem>
|
|---|
| 64 | </varlistentry>
|
|---|
| 65 | <varlistentry>
|
|---|
| 66 | <term>schema_mode = <rfc2307 | sfu ></term>
|
|---|
| 67 | <listitem><para>
|
|---|
| 68 | Defines the schema that idmap_ad should use when querying
|
|---|
| 69 | Active Directory regarding user and group information.
|
|---|
| 70 | This can be either the RFC2307 schema support included
|
|---|
| 71 | in Windows 2003 R2 or the Service for Unix (SFU) schema.
|
|---|
| 72 | </para></listitem>
|
|---|
| 73 | </varlistentry>
|
|---|
| 74 | </variablelist>
|
|---|
| 75 | </refsect1>
|
|---|
| 76 |
|
|---|
| 77 | <refsect1>
|
|---|
| 78 | <title>EXAMPLES</title>
|
|---|
| 79 | <para>
|
|---|
| 80 | The following example shows how to retrieve idmappings from our principal and
|
|---|
| 81 | trusted AD domains. If trusted domains are present id conflicts must be
|
|---|
| 82 | resolved beforehand, there is no
|
|---|
| 83 | guarantee on the order conflicting mappings would be resolved at this point.
|
|---|
| 84 |
|
|---|
| 85 | This example also shows how to leave a small non conflicting range for local
|
|---|
| 86 | id allocation that may be used in internal backends like BUILTIN.
|
|---|
| 87 | </para>
|
|---|
| 88 |
|
|---|
| 89 | <programlisting>
|
|---|
| 90 | [global]
|
|---|
| 91 | idmap config * : backend = tdb
|
|---|
| 92 | idmap config * : range = 1000000-1999999
|
|---|
| 93 |
|
|---|
| 94 | idmap config CORP : backend = ad
|
|---|
| 95 | idmap config CORP : range = 1000-999999
|
|---|
| 96 | </programlisting>
|
|---|
| 97 | </refsect1>
|
|---|
| 98 |
|
|---|
| 99 | <refsect1>
|
|---|
| 100 | <title>AUTHOR</title>
|
|---|
| 101 |
|
|---|
| 102 | <para>
|
|---|
| 103 | The original Samba software and related utilities
|
|---|
| 104 | were created by Andrew Tridgell. Samba is now developed
|
|---|
| 105 | by the Samba Team as an Open Source project similar
|
|---|
| 106 | to the way the Linux kernel is developed.
|
|---|
| 107 | </para>
|
|---|
| 108 | </refsect1>
|
|---|
| 109 |
|
|---|
| 110 | </refentry>
|
|---|
