1 | '\" t
|
---|
2 | .\" Title: idmap_ad
|
---|
3 | .\" Author: [see the "AUTHOR" section]
|
---|
4 | .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
|
---|
5 | .\" Date: 10/29/2012
|
---|
6 | .\" Manual: System Administration tools
|
---|
7 | .\" Source: Samba 3.6
|
---|
8 | .\" Language: English
|
---|
9 | .\"
|
---|
10 | .TH "IDMAP_AD" "8" "10/29/2012" "Samba 3\&.6" "System Administration tools"
|
---|
11 | .\" -----------------------------------------------------------------
|
---|
12 | .\" * set default formatting
|
---|
13 | .\" -----------------------------------------------------------------
|
---|
14 | .\" disable hyphenation
|
---|
15 | .nh
|
---|
16 | .\" disable justification (adjust text to left margin only)
|
---|
17 | .ad l
|
---|
18 | .\" -----------------------------------------------------------------
|
---|
19 | .\" * MAIN CONTENT STARTS HERE *
|
---|
20 | .\" -----------------------------------------------------------------
|
---|
21 | .SH "NAME"
|
---|
22 | idmap_ad \- Samba\'s idmap_ad Backend for Winbind
|
---|
23 | .SH "DESCRIPTION"
|
---|
24 | .PP
|
---|
25 | The idmap_ad plugin provides a way for Winbind to read id mappings from an AD server that uses RFC2307/SFU schema extensions\&. This module implements only the "idmap" API, and is READONLY\&. Mappings must be provided in advance by the administrator by adding the posixAccount/posixGroup classes and relative attribute/value pairs to the user and group objects in the AD\&.
|
---|
26 | .PP
|
---|
27 | Note that the idmap_ad module has changed considerably since Samba versions 3\&.0 and 3\&.2\&. Currently, the
|
---|
28 | \fIad\fR
|
---|
29 | backend does not work as the the default idmap backend, but one has to configure it separately for each domain for which one wants to use it, using disjoint ranges\&. One usually needs to configure a writeable default idmap range, using for example the
|
---|
30 | \fItdb\fR
|
---|
31 | or
|
---|
32 | \fIldap\fR
|
---|
33 | backend, in order to be able to map the BUILTIN sids and possibly other trusted domains\&. The writeable default config is also needed in order to be able to create group mappings\&. This catch\-all default idmap configuration should have a range that is disjoint from any explicitly configured domain with idmap backend
|
---|
34 | \fIad\fR\&. See the example below\&.
|
---|
35 | .SH "IDMAP OPTIONS"
|
---|
36 | .PP
|
---|
37 | range = low \- high
|
---|
38 | .RS 4
|
---|
39 | Defines the available matching UID and GID range for which the backend is authoritative\&. Note that the range acts as a filter\&. If specified any UID or GID stored in AD that fall outside the range is ignored and the corresponding map is discarded\&. It is intended as a way to avoid accidental UID/GID overlaps between local and remotely defined IDs\&.
|
---|
40 | .RE
|
---|
41 | .PP
|
---|
42 | schema_mode = <rfc2307 | sfu >
|
---|
43 | .RS 4
|
---|
44 | Defines the schema that idmap_ad should use when querying Active Directory regarding user and group information\&. This can be either the RFC2307 schema support included in Windows 2003 R2 or the Service for Unix (SFU) schema\&.
|
---|
45 | .RE
|
---|
46 | .SH "EXAMPLES"
|
---|
47 | .PP
|
---|
48 | The following example shows how to retrieve idmappings from our principal and trusted AD domains\&. If trusted domains are present id conflicts must be resolved beforehand, there is no guarantee on the order conflicting mappings would be resolved at this point\&. This example also shows how to leave a small non conflicting range for local id allocation that may be used in internal backends like BUILTIN\&.
|
---|
49 | .sp
|
---|
50 | .if n \{\
|
---|
51 | .RS 4
|
---|
52 | .\}
|
---|
53 | .nf
|
---|
54 | [global]
|
---|
55 | idmap config * : backend = tdb
|
---|
56 | idmap config * : range = 1000000\-1999999
|
---|
57 |
|
---|
58 | idmap config CORP : backend = ad
|
---|
59 | idmap config CORP : range = 1000\-999999
|
---|
60 |
|
---|
61 | .fi
|
---|
62 | .if n \{\
|
---|
63 | .RE
|
---|
64 | .\}
|
---|
65 | .SH "AUTHOR"
|
---|
66 | .PP
|
---|
67 | 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\&.
|
---|