source: vendor/current/docs/manpages/idmap_ad.8

Last change on this file was 989, checked in by Silvan Scherrer, 9 years ago

Samba Server: update vendor to version 4.4.7

File size: 4.2 KB
RevLine 
[860]1'\" t
2.\" Title: idmap_ad
3.\" Author: [see the "AUTHOR" section]
[988]4.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
[989]5.\" Date: 10/25/2016
[860]6.\" Manual: System Administration tools
[988]7.\" Source: Samba 4.4
[860]8.\" Language: English
9.\"
[989]10.TH "IDMAP_AD" "8" "10/25/2016" "Samba 4\&.4" "System Administration tools"
[860]11.\" -----------------------------------------------------------------
12.\" * Define some portability stuff
13.\" -----------------------------------------------------------------
14.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15.\" http://bugs.debian.org/507673
16.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18.ie \n(.g .ds Aq \(aq
19.el .ds Aq '
20.\" -----------------------------------------------------------------
21.\" * set default formatting
22.\" -----------------------------------------------------------------
23.\" disable hyphenation
24.nh
25.\" disable justification (adjust text to left margin only)
26.ad l
27.\" -----------------------------------------------------------------
28.\" * MAIN CONTENT STARTS HERE *
29.\" -----------------------------------------------------------------
30.SH "NAME"
31idmap_ad \- Samba\*(Aqs idmap_ad Backend for Winbind
32.SH "DESCRIPTION"
33.PP
34The 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 uidNumber attributes for users and gidNumber attributes for groups in the AD\&. Winbind will only map users that have a uidNumber and whose primary group have a gidNumber attribute set\&. It is however recommended that all groups in use have gidNumber attributes assigned, otherwise they are not working\&.
35.PP
[988]36Currently, the
[860]37\fIad\fR
[988]38backend does not work as 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
[860]39\fItdb\fR
40or
41\fIldap\fR
42backend, 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
43\fIad\fR\&. See the example below\&.
44.SH "IDMAP OPTIONS"
45.PP
46range = low \- high
47.RS 4
48Defines 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\&.
49.RE
50.PP
[988]51schema_mode = <rfc2307 | sfu | sfu20>
[860]52.RS 4
[988]53Defines 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\&. For SFU 3\&.0 or 3\&.5 please choose "sfu", for SFU 2\&.0 please choose "sfu20"\&. Please note that primary group membership is currently always calculated via the "primaryGroupID" LDAP attribute\&.
[860]54.RE
55.SH "EXAMPLES"
56.PP
57The 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\&.
58.sp
59.if n \{\
60.RS 4
61.\}
62.nf
63 [global]
[988]64 workgroup = CORP
65
[860]66 idmap config * : backend = tdb
67 idmap config * : range = 1000000\-1999999
68
69 idmap config CORP : backend = ad
70 idmap config CORP : range = 1000\-999999
71
72.fi
73.if n \{\
74.RE
75.\}
76.SH "AUTHOR"
77.PP
78The 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\&.
Note: See TracBrowser for help on using the repository browser.