1IDMAP_LDAP(8) System Administration tools IDMAP_LDAP(8)
2
3
4
6 idmap_ldap - Samba´s idmap_ldap Backend for Winbind
7
9 The idmap_ldap plugin provides a means for Winbind to store and
10 retrieve SID/uid/gid mapping tables in an LDAP directory service.
11
12 In contrast to read only backends like idmap_rid, it is an allocating
13 backend: This means that it needs to allocate new user and group IDs in
14 order to create new mappings. The allocator can be provided by the
15 idmap_ldap backend itself or by any other allocating backend like
16 idmap_tdb or idmap_tdb2. This is configured with the parameter idmap
17 alloc backend.
18
19 Note that in order for this (or any other allocating) backend to
20 function at all, the default backend needs to be writeable. The ranges
21 used for uid and gid allocation are the default ranges configured by
22 "idmap uid" and "idmap gid".
23
24 Furthermore, since there is only one global allocating backend
25 responsible for all domains using writeable idmap backends, any
26 explicitly configured domain with idmap backend ldap should have the
27 same range as the default range, since it needs to use the global uid /
28 gid allocator. See the example below.
29
31 ldap_base_dn = DN
32 Defines the directory base suffix to use when searching for
33 SID/uid/gid mapping entries. If not defined, idmap_ldap will
34 default to using the "ldap idmap suffix" option from smb.conf.
35
36 ldap_user_dn = DN
37 Defines the user DN to be used for authentication. If absent an
38 anonymous bind will be performed.
39
40 ldap_url = ldap://server/
41 Specifies the LDAP server to use when searching for existing
42 SID/uid/gid map entries. If not defined, idmap_ldap will assume
43 that ldap://localhost/ should be used.
44
45 range = low - high
46 Defines the available matching uid and gid range for which the
47 backend is authoritative. If the parameter is absent, Winbind fails
48 over to use the "idmap uid" and "idmap gid" options from smb.conf.
49
51 ldap_base_dn = DN
52 Defines the directory base suffix under which new SID/uid/gid
53 mapping entries should be stored. If not defined, idmap_ldap will
54 default to using the "ldap idmap suffix" option from smb.conf.
55
56 ldap_user_dn = DN
57 Defines the user DN to be used for authentication. If absent an
58 anonymous bind will be performed.
59
60 ldap_url = ldap://server/
61 Specifies the LDAP server to which modify/add/delete requests
62 should be sent. If not defined, idmap_ldap will assume that
63 ldap://localhost/ should be used.
64
66 The follow sets of a LDAP configuration which uses two LDAP
67 directories, one for storing the ID mappings and one for retrieving new
68 IDs.
69
70 [global]
71 idmap backend = ldap:ldap://localhost/
72 idmap uid = 1000000-1999999
73 idmap gid = 1000000-1999999
74
75 idmap alloc backend = ldap
76 idmap alloc config : ldap_url = ldap://id-master/
77 idmap alloc config : ldap_base_dn = ou=idmap,dc=example,dc=com
78
79
81 In order to use authentication against ldap servers you may need to
82 provide a DN and a password. To avoid exposing the password in plain
83 text in the configuration file we store it into a security store. The
84 "net idmap " command is used to store a secret for the DN specified in
85 a specific idmap domain.
86
88 The original Samba software and related utilities were created by
89 Andrew Tridgell. Samba is now developed by the Samba Team as an Open
90 Source project similar to the way the Linux kernel is developed.
91
92
93
94Samba 3.5 08/02/2011 IDMAP_LDAP(8)