1IDMAP_RFC2307(8) System Administration tools IDMAP_RFC2307(8)
2
6 idmap_rfc2307 - Samba´s idmap_rfc2307 Backend for Winbind
7
9 The idmap_rfc2307 plugin provides a way for winbind to read id mappings
10 from records in an LDAP server as defined in RFC 2307. The LDAP server
11 can be stand-alone or the LDAP server provided by the AD server. An AD
12 server is always required to provide the mapping between name and SID,
13 and the LDAP server is queried for the mapping between name and
14 uid/gid. This module implements only the "idmap" API, and is READONLY.
15 Mappings must be provided in advance by the administrator by creating
17 the user accounts in the Active Directory server and the posixAccount
18 and posixGroup objects in the LDAP server. The names in the Active
19 Directory server and in the LDAP server have to be the same.
20 This id mapping approach allows the reuse of existing LDAP
22 authentication servers that store records in the RFC 2307 format.
23
25 range = low - high
26 Defines the available matching UID and GID range for which the
27 backend is authoritative. Note that the range acts as a filter. If
28 specified any UID or GID stored in AD that fall outside the range
29 is ignored and the corresponding map is discarded. It is intended
30 as a way to avoid accidental UID/GID overlaps between local and
31 remotely defined IDs.
32 ldap_server = <ad | stand-alone >
34 Defines the type of LDAP server to use. This can either be the LDAP
35 server provided by the Active Directory server (ad) or a
36 stand-alone LDAP server.
37 bind_path_user
39 Specifies the bind path where user objects can be found in the LDAP
40 server.
41 bind_path_group
43 Specifies the bind path where group objects can be found in the
44 LDAP server.
45 user_cn = <yes | no>
47 Query cn attribute instead of uid attribute for the user name in
48 LDAP. This option is not required, the default is no.
49 cn_realm = <yes | no>
51 Append @realm to cn for groups (and users if user_cn is set) in
52 LDAP. This option is not required, the default is no.
53 ldap_domain
55 When using the LDAP server in the Active Directory server, this
56 allows to specify the domain where to access the Active Directory
57 server. This allows using trust relationships while keeping all RFC
58 2307 records in one place. This parameter is optional, the default
59 is to access the AD server in the current domain to query LDAP
60 records.
61 ldap_url
63 When using a stand-alone LDAP server, this parameter specifies the
64 ldap URL for accessing the LDAP server.
65 ldap_user_dn
67 Defines the user DN to be used for authentication. The secret for
68 authenticating this user should be stored with net idmap secret
69 (see net(8)). If absent, an anonymous bind will be performed.
70 ldap_realm
72 Defines the realm to use in the user and group names. This is only
73 required when using cn_realm together with a stand-alone ldap
74 server.
75
77 The following example shows how to retrieve id mappings from a
78 stand-alone LDAP server. This example also shows how to leave a small
79 non conflicting range for local id allocation that may be used in
80 internal backends like BUILTIN.
81 [global]
83 idmap config * : backend = tdb
84 idmap config * : range = 1000000-1999999
85 idmap config DOMAIN : backend = rfc2307
87 idmap config DOMAIN : range = 2000000-2999999
88 idmap config DOMAIN : ldap_server = stand-alone
89 idmap config DOMAIN : ldap_url = ldap://ldap1.example.com
90 idmap config DOMAIN : ldap_user_dn = cn=ldapmanager,dc=example,dc=com
91 idmap config DOMAIN : bind_path_user = ou=People,dc=example,dc=com
92 idmap config DOMAIN : bind_path_group = ou=Group,dc=example,dc=com
93
96 The original Samba software and related utilities were created by
97 Andrew Tridgell. Samba is now developed by the Samba Team as an Open
98 Source project similar to the way the Linux kernel is developed.
99Samba 4.2 06/19/2018 IDMAP_RFC2307(8)