- Timestamp:
- Nov 12, 2012, 7:37:04 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.5.x/docs/htmldocs/Samba3-HOWTO/idmapper.html
r599 r739 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 14. Identity Mapping (IDMAP)</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command"><link rel="next" href="rights.html" title="Chapter 15. User Rights and Privileges"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 14. Identity Mapping (IDMAP)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetCommand.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="rights.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 14. Identity Mapping (IDMAP)"><div class="titlepage"><div><div><h2 class="title"><a name="idmapper"></a>Chapter 14. Identity Mapping (IDMAP)</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="idmapper.html#id37 2830">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id372854">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id372912">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id373803">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id374021">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id374087">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id374148">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id374842">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id375401">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id375947">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></div><p>2 <a class="indexterm" name="id37 2576"></a>3 <a class="indexterm" name="id37 2582"></a>4 <a class="indexterm" name="id37 2589"></a>5 <a class="indexterm" name="id37 2596"></a>6 <a class="indexterm" name="id37 2605"></a>7 <a class="indexterm" name="id37 2612"></a>8 <a class="indexterm" name="id37 2618"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 14. Identity Mapping (IDMAP)</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command"><link rel="next" href="rights.html" title="Chapter 15. User Rights and Privileges"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 14. Identity Mapping (IDMAP)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetCommand.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="rights.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 14. Identity Mapping (IDMAP)"><div class="titlepage"><div><div><h2 class="title"><a name="idmapper"></a>Chapter 14. Identity Mapping (IDMAP)</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="idmapper.html#id370980">Samba Server Deployment Types and IDMAP</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id371003">Standalone Samba Server</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id371061">Domain Member Server or Domain Member Client</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id371952">Primary Domain Controller</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id372170">Backup Domain Controller</a></span></dt></dl></dd><dt><span class="sect1"><a href="idmapper.html#id372236">Examples of IDMAP Backend Usage</a></span></dt><dd><dl><dt><span class="sect2"><a href="idmapper.html#id372297">Default Winbind TDB</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id372991">IDMAP_RID with Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id373550">IDMAP Storage in LDAP Using Winbind</a></span></dt><dt><span class="sect2"><a href="idmapper.html#id374095">IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id370725"></a> 3 <a class="indexterm" name="id370732"></a> 4 <a class="indexterm" name="id370739"></a> 5 <a class="indexterm" name="id370745"></a> 6 <a class="indexterm" name="id370754"></a> 7 <a class="indexterm" name="id370761"></a> 8 <a class="indexterm" name="id370768"></a> 9 9 The Microsoft Windows operating system has a number of features that impose specific challenges 10 10 to interoperability with the operating systems on which Samba is implemented. This chapter deals … … 17 17 This is followed by an overview of how the IDMAP facility may be implemented. 18 18 </p><p> 19 <a class="indexterm" name="id37 2637"></a>20 <a class="indexterm" name="id37 2644"></a>21 <a class="indexterm" name="id37 2650"></a>22 <a class="indexterm" name="id37 2657"></a>19 <a class="indexterm" name="id370786"></a> 20 <a class="indexterm" name="id370793"></a> 21 <a class="indexterm" name="id370800"></a> 22 <a class="indexterm" name="id370807"></a> 23 23 The IDMAP facility is of concern where more than one Samba server (or Samba network client) 24 24 is installed in a domain. Where there is a single Samba server, do not be too concerned regarding … … 27 27 another, and that is where the fun begins! 28 28 </p><p> 29 <a class="indexterm" name="id37 2674"></a>30 <a class="indexterm" name="id37 2680"></a>31 <a class="indexterm" name="id37 2686"></a>32 <a class="indexterm" name="id37 2693"></a>33 <a class="indexterm" name="id37 2700"></a>34 <a class="indexterm" name="id37 2707"></a>35 <a class="indexterm" name="id37 2713"></a>36 <a class="indexterm" name="id37 2720"></a>29 <a class="indexterm" name="id370824"></a> 30 <a class="indexterm" name="id370829"></a> 31 <a class="indexterm" name="id370836"></a> 32 <a class="indexterm" name="id370843"></a> 33 <a class="indexterm" name="id370849"></a> 34 <a class="indexterm" name="id370856"></a> 35 <a class="indexterm" name="id370863"></a> 36 <a class="indexterm" name="id370870"></a> 37 37 Where user and group account information is stored in an LDAP directory every server can have the same 38 38 consistent UID and GID for users and groups. This is achieved using NSS and the nss_ldap tool. Samba … … 42 42 or if there is a need to keep the security name-space separate (i.e., the user 43 43 <code class="literal">DOMINICUS\FJones</code> must not be given access to the account resources of the user 44 <code class="literal">FRANCISCUS\FJones</code><sup>[<a name="id37 2743" href="#ftn.id372743" class="footnote">4</a>]</sup> free from inadvertent cross-over, close attention should be given44 <code class="literal">FRANCISCUS\FJones</code><sup>[<a name="id370893" href="#ftn.id370893" class="footnote">4</a>]</sup> free from inadvertent cross-over, close attention should be given 45 45 to the way that the IDMAP facility is configured. 46 46 </p><p> 47 <a class="indexterm" name="id37 2770"></a>48 <a class="indexterm" name="id37 2777"></a>49 <a class="indexterm" name="id37 2784"></a>50 <a class="indexterm" name="id37 2790"></a>51 <a class="indexterm" name="id37 2797"></a>52 <a class="indexterm" name="id37 2803"></a>47 <a class="indexterm" name="id370920"></a> 48 <a class="indexterm" name="id370926"></a> 49 <a class="indexterm" name="id370933"></a> 50 <a class="indexterm" name="id370940"></a> 51 <a class="indexterm" name="id370946"></a> 52 <a class="indexterm" name="id370953"></a> 53 53 The use of IDMAP is important where the Samba server will be accessed by workstations or servers from 54 54 more than one domain, in which case it is important to run winbind so it can handle the resolution (ID mapping) 55 55 of foreign SIDs to local UNIX UIDs and GIDs. 56 56 </p><p> 57 <a class="indexterm" name="id37 2816"></a>57 <a class="indexterm" name="id370965"></a> 58 58 The use of the IDMAP facility requires the execution of the <code class="literal">winbindd</code> upon Samba startup. 59 </p><div class="sect1" title="Samba Server Deployment Types and IDMAP"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id37 2830"></a>Samba Server Deployment Types and IDMAP</h2></div></div></div><p>60 <a class="indexterm" name="id37 2838"></a>59 </p><div class="sect1" title="Samba Server Deployment Types and IDMAP"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id370980"></a>Samba Server Deployment Types and IDMAP</h2></div></div></div><p> 60 <a class="indexterm" name="id370987"></a> 61 61 There are four basic server deployment types, as documented in <a class="link" href="ServerType.html" title="Chapter 3. Server Types and Security Modes">the chapter 62 62 on Server Types and Security Modes</a>. 63 </p><div class="sect2" title="Standalone Samba Server"><div class="titlepage"><div><div><h3 class="title"><a name="id37 2854"></a>Standalone Samba Server</h3></div></div></div><p>64 <a class="indexterm" name="id37 2861"></a>65 <a class="indexterm" name="id37 2868"></a>66 <a class="indexterm" name="id37 2875"></a>63 </p><div class="sect2" title="Standalone Samba Server"><div class="titlepage"><div><div><h3 class="title"><a name="id371003"></a>Standalone Samba Server</h3></div></div></div><p> 64 <a class="indexterm" name="id371011"></a> 65 <a class="indexterm" name="id371017"></a> 66 <a class="indexterm" name="id371024"></a> 67 67 A standalone Samba server is an implementation that is not a member of a Windows NT4 domain, 68 68 a Windows 200X Active Directory domain, or a Samba domain. 69 69 </p><p> 70 <a class="indexterm" name="id37 2886"></a>71 <a class="indexterm" name="id37 2893"></a>72 <a class="indexterm" name="id37 2900"></a>70 <a class="indexterm" name="id371036"></a> 71 <a class="indexterm" name="id371042"></a> 72 <a class="indexterm" name="id371049"></a> 73 73 By definition, this means that users and groups will be created and controlled locally, and 74 74 the identity of a network user must match a local UNIX/Linux user login. The IDMAP facility 75 75 is therefore of little to no interest, winbind will not be necessary, and the IDMAP facility 76 76 will not be relevant or of interest. 77 </p></div><div class="sect2" title="Domain Member Server or Domain Member Client"><div class="titlepage"><div><div><h3 class="title"><a name="id37 2912"></a>Domain Member Server or Domain Member Client</h3></div></div></div><p>78 <a class="indexterm" name="id37 2920"></a>79 <a class="indexterm" name="id37 2926"></a>80 <a class="indexterm" name="id37 2933"></a>81 <a class="indexterm" name="id37 2940"></a>82 <a class="indexterm" name="id37 2946"></a>77 </p></div><div class="sect2" title="Domain Member Server or Domain Member Client"><div class="titlepage"><div><div><h3 class="title"><a name="id371061"></a>Domain Member Server or Domain Member Client</h3></div></div></div><p> 78 <a class="indexterm" name="id371069"></a> 79 <a class="indexterm" name="id371076"></a> 80 <a class="indexterm" name="id371082"></a> 81 <a class="indexterm" name="id371089"></a> 82 <a class="indexterm" name="id371095"></a> 83 83 Samba-3 can act as a Windows NT4 PDC or BDC, thereby providing domain control protocols that 84 84 are compatible with Windows NT4. Samba-3 file and print sharing protocols are compatible with … … 86 86 extensively makes use of Windows SIDs. 87 87 </p><p> 88 <a class="indexterm" name="id37 2959"></a>89 <a class="indexterm" name="id37 2966"></a>90 <a class="indexterm" name="id37 2972"></a>88 <a class="indexterm" name="id371108"></a> 89 <a class="indexterm" name="id371115"></a> 90 <a class="indexterm" name="id371121"></a> 91 91 Samba-3 domain member servers and clients must interact correctly with MS Windows SIDs. Incoming 92 92 Windows SIDs must be translated to local UNIX UIDs and GIDs. Outgoing information from the Samba 93 93 server must provide to MS Windows clients and servers appropriate SIDs. 94 94 </p><p> 95 <a class="indexterm" name="id37 2984"></a>96 <a class="indexterm" name="id37 2991"></a>95 <a class="indexterm" name="id371133"></a> 96 <a class="indexterm" name="id371140"></a> 97 97 A Samba member of a Windows networking domain (NT4-style or ADS) can be configured to handle 98 98 identity mapping in a variety of ways. The mechanism it uses depends on whether or not … … 100 100 The configuration options are briefly described here: 101 101 </p><div class="variablelist"><dl><dt><span class="term">Winbind is not used; users and groups are local: </span></dt><dd><p> 102 <a class="indexterm" name="id37 3018"></a>103 <a class="indexterm" name="id37 3025"></a>104 <a class="indexterm" name="id37 3032"></a>105 <a class="indexterm" name="id37 3039"></a>106 <a class="indexterm" name="id37 3046"></a>107 <a class="indexterm" name="id37 3052"></a>108 <a class="indexterm" name="id37 3059"></a>109 <a class="indexterm" name="id37 3066"></a>110 <a class="indexterm" name="id37 3073"></a>111 <a class="indexterm" name="id37 3079"></a>112 <a class="indexterm" name="id37 3086"></a>102 <a class="indexterm" name="id371168"></a> 103 <a class="indexterm" name="id371174"></a> 104 <a class="indexterm" name="id371181"></a> 105 <a class="indexterm" name="id371188"></a> 106 <a class="indexterm" name="id371195"></a> 107 <a class="indexterm" name="id371202"></a> 108 <a class="indexterm" name="id371208"></a> 109 <a class="indexterm" name="id371215"></a> 110 <a class="indexterm" name="id371222"></a> 111 <a class="indexterm" name="id371228"></a> 112 <a class="indexterm" name="id371235"></a> 113 113 Where <code class="literal">winbindd</code> is not used Samba (<code class="literal">smbd</code>) 114 114 uses the underlying UNIX/Linux mechanisms to resolve the identity of incoming … … 120 120 <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> respectively. 121 121 </p><p> 122 <a class="indexterm" name="id37 3124"></a>123 <a class="indexterm" name="id37 3131"></a>122 <a class="indexterm" name="id371273"></a> 123 <a class="indexterm" name="id371280"></a> 124 124 For example, when the user <code class="literal">BERYLIUM\WambatW</code> tries to open a 125 125 connection to a Samba server the incoming SessionSetupAndX request will make a … … 127 127 <code class="filename">/etc/passwd</code> file. 128 128 </p><p> 129 <a class="indexterm" name="id37 3160"></a>130 <a class="indexterm" name="id37 3167"></a>131 <a class="indexterm" name="id37 3174"></a>132 <a class="indexterm" name="id37 3181"></a>133 <a class="indexterm" name="id37 3187"></a>134 <a class="indexterm" name="id37 3194"></a>135 <a class="indexterm" name="id37 3200"></a>136 <a class="indexterm" name="id37 3207"></a>129 <a class="indexterm" name="id371310"></a> 130 <a class="indexterm" name="id371316"></a> 131 <a class="indexterm" name="id371323"></a> 132 <a class="indexterm" name="id371330"></a> 133 <a class="indexterm" name="id371336"></a> 134 <a class="indexterm" name="id371343"></a> 135 <a class="indexterm" name="id371350"></a> 136 <a class="indexterm" name="id371356"></a> 137 137 This configuration may be used with standalone Samba servers, domain member 138 138 servers (NT4 or ADS), and for a PDC that uses either an smbpasswd 139 139 or a tdbsam-based Samba passdb backend. 140 140 </p></dd><dt><span class="term">Winbind is not used; users and groups resolved via NSS: </span></dt><dd><p> 141 <a class="indexterm" name="id37 3228"></a>142 <a class="indexterm" name="id37 3235"></a>143 <a class="indexterm" name="id37 3242"></a>144 <a class="indexterm" name="id37 3249"></a>145 <a class="indexterm" name="id37 3255"></a>146 <a class="indexterm" name="id37 3262"></a>141 <a class="indexterm" name="id371377"></a> 142 <a class="indexterm" name="id371384"></a> 143 <a class="indexterm" name="id371391"></a> 144 <a class="indexterm" name="id371398"></a> 145 <a class="indexterm" name="id371404"></a> 146 <a class="indexterm" name="id371411"></a> 147 147 In this situation user and group accounts are treated as if they are local 148 148 accounts. The only way in which this differs from having local accounts is … … 150 150 this means that they will reside in either an NIS-type database or else in LDAP. 151 151 </p><p> 152 <a class="indexterm" name="id37 3275"></a>153 <a class="indexterm" name="id37 3282"></a>154 <a class="indexterm" name="id37 3288"></a>155 <a class="indexterm" name="id37 3295"></a>156 <a class="indexterm" name="id37 3302"></a>157 <a class="indexterm" name="id37 3308"></a>158 <a class="indexterm" name="id37 3315"></a>152 <a class="indexterm" name="id371424"></a> 153 <a class="indexterm" name="id371431"></a> 154 <a class="indexterm" name="id371438"></a> 155 <a class="indexterm" name="id371444"></a> 156 <a class="indexterm" name="id371451"></a> 157 <a class="indexterm" name="id371457"></a> 158 <a class="indexterm" name="id371464"></a> 159 159 This configuration may be used with standalone Samba servers, domain member 160 160 servers (NT4 or ADS), and for a PDC that uses either an smbpasswd 161 161 or a tdbsam-based Samba passdb backend. 162 162 </p></dd><dt><span class="term">Winbind/NSS with the default local IDMAP table: </span></dt><dd><p> 163 <a class="indexterm" name="id37 3336"></a>164 <a class="indexterm" name="id37 3342"></a>165 <a class="indexterm" name="id37 3349"></a>166 <a class="indexterm" name="id37 3356"></a>163 <a class="indexterm" name="id371485"></a> 164 <a class="indexterm" name="id371492"></a> 165 <a class="indexterm" name="id371498"></a> 166 <a class="indexterm" name="id371505"></a> 167 167 There are many sites that require only a simple Samba server or a single Samba 168 168 server that is a member of a Windows NT4 domain or an ADS domain. A typical example … … 172 172 Active Directory. 173 173 </p><p> 174 <a class="indexterm" name="id37 3370"></a>175 <a class="indexterm" name="id37 3377"></a>176 <a class="indexterm" name="id37 3384"></a>177 <a class="indexterm" name="id37 3390"></a>178 <a class="indexterm" name="id37 3397"></a>174 <a class="indexterm" name="id371519"></a> 175 <a class="indexterm" name="id371526"></a> 176 <a class="indexterm" name="id371533"></a> 177 <a class="indexterm" name="id371540"></a> 178 <a class="indexterm" name="id371546"></a> 179 179 Winbind is a great convenience in this situation. All that is needed is a range of 180 180 UID numbers and GID numbers that can be defined in the <code class="filename">smb.conf</code> file. The … … 183 183 The SIDs are allocated a UID/GID in the order in which winbind receives them. 184 184 </p><p> 185 <a class="indexterm" name="id37 3428"></a>186 <a class="indexterm" name="id37 3434"></a>187 <a class="indexterm" name="id37 3441"></a>188 <a class="indexterm" name="id37 3448"></a>185 <a class="indexterm" name="id371577"></a> 186 <a class="indexterm" name="id371583"></a> 187 <a class="indexterm" name="id371590"></a> 188 <a class="indexterm" name="id371597"></a> 189 189 This configuration is not convenient or practical in sites that have more than one 190 190 Samba server and that require the same UID or GID for the same user or group across … … 195 195 the rightful owners. 196 196 </p></dd><dt><span class="term">Winbind/NSS uses RID based IDMAP: </span></dt><dd><p> 197 <a class="indexterm" name="id37 3471"></a>198 <a class="indexterm" name="id37 3478"></a>199 <a class="indexterm" name="id37 3485"></a>200 <a class="indexterm" name="id37 3491"></a>197 <a class="indexterm" name="id371620"></a> 198 <a class="indexterm" name="id371627"></a> 199 <a class="indexterm" name="id371634"></a> 200 <a class="indexterm" name="id371640"></a> 201 201 The IDMAP_RID facility is new to Samba version 3.0.8. It was added to make life easier 202 202 for a number of sites that are committed to use of MS ADS, that do not apply … … 206 206 IDMAP table problem, then IDMAP_RID is an obvious choice. 207 207 </p><p> 208 <a class="indexterm" name="id37 3506"></a>209 <a class="indexterm" name="id37 3513"></a>210 <a class="indexterm" name="id37 3519"></a>211 <a class="indexterm" name="id37 3526"></a>212 <a class="indexterm" name="id37 3533"></a>213 <a class="indexterm" name="id37 3539"></a>214 <a class="indexterm" name="id37 3546"></a>215 <a class="indexterm" name="id37 3553"></a>208 <a class="indexterm" name="id371655"></a> 209 <a class="indexterm" name="id371662"></a> 210 <a class="indexterm" name="id371668"></a> 211 <a class="indexterm" name="id371675"></a> 212 <a class="indexterm" name="id371682"></a> 213 <a class="indexterm" name="id371688"></a> 214 <a class="indexterm" name="id371695"></a> 215 <a class="indexterm" name="id371702"></a> 216 216 This facility requires the allocation of the <em class="parameter"><code>idmap uid</code></em> and the 217 217 <em class="parameter"><code>idmap gid</code></em> ranges, and within the <em class="parameter"><code>idmap uid</code></em> … … 223 223 the resulting UID will be <code class="constant">1000 + 1234 = 2234</code>. 224 224 </p></dd><dt><span class="term">Winbind with an NSS/LDAP backend-based IDMAP facility: </span></dt><dd><p> 225 <a class="indexterm" name="id37 3616"></a>226 <a class="indexterm" name="id37 3623"></a>227 <a class="indexterm" name="id37 3630"></a>228 <a class="indexterm" name="id37 3636"></a>229 <a class="indexterm" name="id37 3643"></a>230 <a class="indexterm" name="id37 3649"></a>231 <a class="indexterm" name="id37 3656"></a>232 <a class="indexterm" name="id37 3663"></a>225 <a class="indexterm" name="id371765"></a> 226 <a class="indexterm" name="id371772"></a> 227 <a class="indexterm" name="id371779"></a> 228 <a class="indexterm" name="id371785"></a> 229 <a class="indexterm" name="id371792"></a> 230 <a class="indexterm" name="id371798"></a> 231 <a class="indexterm" name="id371805"></a> 232 <a class="indexterm" name="id371812"></a> 233 233 In this configuration <code class="literal">winbind</code> resolved SIDs to UIDs and GIDs from 234 234 the <em class="parameter"><code>idmap uid</code></em> and <em class="parameter"><code>idmap gid</code></em> ranges specified … … 237 237 a common IDMAP table. 238 238 </p><p> 239 <a class="indexterm" name="id37 3699"></a>240 <a class="indexterm" name="id37 3706"></a>241 <a class="indexterm" name="id37 3713"></a>239 <a class="indexterm" name="id371848"></a> 240 <a class="indexterm" name="id371855"></a> 241 <a class="indexterm" name="id371862"></a> 242 242 It is important that all LDAP IDMAP clients use only the master LDAP server because the 243 243 <em class="parameter"><code>idmap backend</code></em> facility in the <code class="filename">smb.conf</code> file does not correctly … … 248 248 SIDs are consistent across all servers. 249 249 </p><p> 250 <a class="indexterm" name="id37 3750"></a>251 <a class="indexterm" name="id37 3757"></a>250 <a class="indexterm" name="id371900"></a> 251 <a class="indexterm" name="id371906"></a> 252 252 The use of the LDAP-based passdb backend requires use of the PADL nss_ldap utility or 253 253 an equivalent. In this situation winbind is used to handle foreign SIDs, that is, SIDs from … … 256 256 in precisely the same manner as when using winbind with a local IDMAP table. 257 257 </p><p> 258 <a class="indexterm" name="id37 3771"></a>259 <a class="indexterm" name="id37 3778"></a>260 <a class="indexterm" name="id37 3785"></a>258 <a class="indexterm" name="id371920"></a> 259 <a class="indexterm" name="id371927"></a> 260 <a class="indexterm" name="id371934"></a> 261 261 The nss_ldap tool set can be used to access UIDs and GIDs via LDAP as well as via Active 262 262 Directory. In order to use Active Directory, it is necessary to modify the ADS schema by … … 267 267 Management tool. Each account must be separately UNIX-enabled before the UID and GID data can 268 268 be used by Samba. 269 </p></dd></dl></div></div><div class="sect2" title="Primary Domain Controller"><div class="titlepage"><div><div><h3 class="title"><a name="id37 3803"></a>Primary Domain Controller</h3></div></div></div><p>270 <a class="indexterm" name="id37 3810"></a>271 <a class="indexterm" name="id37 3817"></a>272 <a class="indexterm" name="id37 3824"></a>273 <a class="indexterm" name="id37 3830"></a>269 </p></dd></dl></div></div><div class="sect2" title="Primary Domain Controller"><div class="titlepage"><div><div><h3 class="title"><a name="id371952"></a>Primary Domain Controller</h3></div></div></div><p> 270 <a class="indexterm" name="id371960"></a> 271 <a class="indexterm" name="id371966"></a> 272 <a class="indexterm" name="id371973"></a> 273 <a class="indexterm" name="id371979"></a> 274 274 Microsoft Windows domain security systems generate the user and group SID as part 275 275 of the process of creation of an account. Windows does not have a concept of the UNIX UID or a GID; rather, … … 279 279 in the <code class="filename">smb.conf</code> file, plus twice (2x) the UID or GID. This method is called <span class="quote">“<span class="quote">algorithmic mapping</span>”</span>. 280 280 </p><p> 281 <a class="indexterm" name="id37 3855"></a>281 <a class="indexterm" name="id372004"></a> 282 282 For example, if a user has a UID of 4321, and the algorithmic RID base has a value of 1000, the RID will 283 283 be <code class="literal">1000 + (2 x 4321) = 9642</code>. Thus, if the domain SID is … … 285 285 <code class="literal">S-1-5-21-89238497-92787123-12341112-9642</code>. 286 286 </p><p> 287 <a class="indexterm" name="id37 3884"></a>288 <a class="indexterm" name="id37 3891"></a>289 <a class="indexterm" name="id37 3898"></a>290 <a class="indexterm" name="id37 3904"></a>287 <a class="indexterm" name="id372033"></a> 288 <a class="indexterm" name="id372040"></a> 289 <a class="indexterm" name="id372047"></a> 290 <a class="indexterm" name="id372053"></a> 291 291 The foregoing type of SID is produced by Samba as an automatic function and is either produced on the fly 292 292 (as is the case when using a <em class="parameter"><code>passdb backend = [tdbsam | smbpasswd]</code></em>), or may be stored 293 293 as a permanent part of an account in an LDAP-based ldapsam. 294 294 </p><p> 295 <a class="indexterm" name="id37 3922"></a>296 <a class="indexterm" name="id37 3929"></a>297 <a class="indexterm" name="id37 3936"></a>298 <a class="indexterm" name="id37 3942"></a>299 <a class="indexterm" name="id37 3949"></a>300 <a class="indexterm" name="id37 3956"></a>301 <a class="indexterm" name="id37 3962"></a>302 <a class="indexterm" name="id37 3969"></a>303 <a class="indexterm" name="id37 3976"></a>295 <a class="indexterm" name="id372071"></a> 296 <a class="indexterm" name="id372078"></a> 297 <a class="indexterm" name="id372085"></a> 298 <a class="indexterm" name="id372092"></a> 299 <a class="indexterm" name="id372098"></a> 300 <a class="indexterm" name="id372105"></a> 301 <a class="indexterm" name="id372111"></a> 302 <a class="indexterm" name="id372118"></a> 303 <a class="indexterm" name="id372125"></a> 304 304 ADS uses a directory schema that can be extended to accommodate additional 305 305 account attributes such as UIDs and GIDs. The installation of Microsoft Service for UNIX 3.5 will expand … … 307 307 through a snap-in module to the normal ADS account management MMC interface. 308 308 </p><p> 309 <a class="indexterm" name="id37 3989"></a>310 <a class="indexterm" name="id37 3995"></a>311 <a class="indexterm" name="id37 4002"></a>312 <a class="indexterm" name="id37 4009"></a>309 <a class="indexterm" name="id372138"></a> 310 <a class="indexterm" name="id372144"></a> 311 <a class="indexterm" name="id372151"></a> 312 <a class="indexterm" name="id372158"></a> 313 313 Security identifiers used within a domain must be managed to avoid conflict and to preserve integrity. 314 314 In an NT4 domain context, the PDC manages the distribution of all security credentials to the backup 315 315 domain controllers (BDCs). At this time the only passdb backend for a Samba domain controller that is suitable 316 316 for such information is an LDAP backend. 317 </p></div><div class="sect2" title="Backup Domain Controller"><div class="titlepage"><div><div><h3 class="title"><a name="id37 4021"></a>Backup Domain Controller</h3></div></div></div><p>318 <a class="indexterm" name="id37 4029"></a>319 <a class="indexterm" name="id37 4035"></a>320 <a class="indexterm" name="id37 4042"></a>321 <a class="indexterm" name="id37 4049"></a>322 <a class="indexterm" name="id37 4056"></a>323 <a class="indexterm" name="id37 4062"></a>324 <a class="indexterm" name="id37 4069"></a>317 </p></div><div class="sect2" title="Backup Domain Controller"><div class="titlepage"><div><div><h3 class="title"><a name="id372170"></a>Backup Domain Controller</h3></div></div></div><p> 318 <a class="indexterm" name="id372178"></a> 319 <a class="indexterm" name="id372184"></a> 320 <a class="indexterm" name="id372191"></a> 321 <a class="indexterm" name="id372198"></a> 322 <a class="indexterm" name="id372205"></a> 323 <a class="indexterm" name="id372212"></a> 324 <a class="indexterm" name="id372218"></a> 325 325 BDCs have read-only access to security credentials that are stored in LDAP. 326 326 Changes in user or group account information are passed by the BDC to the PDC. Only the PDC can write … … 331 331 in the IDMAP backend. This means that it is is unsafe to use a slave (replicate) LDAP server with 332 332 the IDMAP facility. 333 </p></div></div><div class="sect1" title="Examples of IDMAP Backend Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id37 4087"></a>Examples of IDMAP Backend Usage</h2></div></div></div><p>334 <a class="indexterm" name="id37 4095"></a>335 <a class="indexterm" name="id37 4104"></a>336 <a class="indexterm" name="id37 4113"></a>337 <a class="indexterm" name="id37 4120"></a>338 <a class="indexterm" name="id37 4126"></a>333 </p></div></div><div class="sect1" title="Examples of IDMAP Backend Usage"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id372236"></a>Examples of IDMAP Backend Usage</h2></div></div></div><p> 334 <a class="indexterm" name="id372244"></a> 335 <a class="indexterm" name="id372253"></a> 336 <a class="indexterm" name="id372262"></a> 337 <a class="indexterm" name="id372269"></a> 338 <a class="indexterm" name="id372275"></a> 339 339 Anyone who wishes to use <code class="literal">winbind</code> will find the following example configurations helpful. 340 340 Remember that in the majority of cases <code class="literal">winbind</code> is of primary interest for use with 341 341 domain member servers (DMSs) and domain member clients (DMCs). 342 </p><div class="sect2" title="Default Winbind TDB"><div class="titlepage"><div><div><h3 class="title"><a name="id37 4148"></a>Default Winbind TDB</h3></div></div></div><p>342 </p><div class="sect2" title="Default Winbind TDB"><div class="titlepage"><div><div><h3 class="title"><a name="id372297"></a>Default Winbind TDB</h3></div></div></div><p> 343 343 Two common configurations are used: 344 344 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> … … 346 346 </p></li><li class="listitem"><p> 347 347 Networks that use MS Windows 200x ADS. 348 </p></li></ul></div><div class="sect3" title="NT4-Style Domains (Includes Samba Domains)"><div class="titlepage"><div><div><h4 class="title"><a name="id37 4170"></a>NT4-Style Domains (Includes Samba Domains)</h4></div></div></div><p>348 </p></li></ul></div><div class="sect3" title="NT4-Style Domains (Includes Samba Domains)"><div class="titlepage"><div><div><h4 class="title"><a name="id372319"></a>NT4-Style Domains (Includes Samba Domains)</h4></div></div></div><p> 349 349 <a class="link" href="idmapper.html#idmapnt4dms" title="Example 14.1. NT4 Domain Member Server smb.conf">NT4 Domain Member Server smb.con</a> is a simple example of an NT4 DMS 350 350 <code class="filename">smb.conf</code> file that shows only the global section. 351 </p><div class="example"><a name="idmapnt4dms"></a><p class="title"><b>Example 14.1. NT4 Domain Member Server smb.conf</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id37 4222"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id374233"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id374244"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id374256"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id374267"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id374279"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"><p>352 <a class="indexterm" name="id37 4294"></a>353 <a class="indexterm" name="id37 4301"></a>351 </p><div class="example"><a name="idmapnt4dms"></a><p class="title"><b>Example 14.1. NT4 Domain Member Server smb.conf</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id372370"></a><em class="parameter"><code>workgroup = MEGANET2</code></em></td></tr><tr><td><a class="indexterm" name="id372382"></a><em class="parameter"><code>security = DOMAIN</code></em></td></tr><tr><td><a class="indexterm" name="id372393"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id372405"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td><a class="indexterm" name="id372416"></a><em class="parameter"><code>template primary group = "Domain Users"</code></em></td></tr><tr><td><a class="indexterm" name="id372428"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"><p> 352 <a class="indexterm" name="id372442"></a> 353 <a class="indexterm" name="id372449"></a> 354 354 The use of <code class="literal">winbind</code> requires configuration of NSS. Edit the <code class="filename">/etc/nsswitch.conf</code> 355 355 so it includes the following entries: … … 374 374 Joined domain MEGANET2. 375 375 </pre><p> 376 <a class="indexterm" name="id37 4365"></a>376 <a class="indexterm" name="id372514"></a> 377 377 The success of the join can be confirmed with the following command: 378 378 </p><pre class="screen"> … … 381 381 </pre><p> 382 382 A failed join would report an error message like the following: 383 <a class="indexterm" name="id37 4385"></a>383 <a class="indexterm" name="id372534"></a> 384 384 </p><pre class="screen"> 385 385 <code class="prompt">root# </code> net rpc testjoin … … 388 388 </pre><p> 389 389 </p></li><li class="step" title="Step 3"><p> 390 <a class="indexterm" name="id37 4411"></a>391 <a class="indexterm" name="id37 4418"></a>392 <a class="indexterm" name="id37 4424"></a>390 <a class="indexterm" name="id372560"></a> 391 <a class="indexterm" name="id372566"></a> 392 <a class="indexterm" name="id372573"></a> 393 393 Start the <code class="literal">nmbd, winbind,</code> and <code class="literal">smbd</code> daemons in the order shown. 394 </p></li></ol></div></div><div class="sect3" title="ADS Domains"><div class="titlepage"><div><div><h4 class="title"><a name="id37 4447"></a>ADS Domains</h4></div></div></div><p>395 <a class="indexterm" name="id37 4455"></a>396 <a class="indexterm" name="id37 4461"></a>394 </p></li></ol></div></div><div class="sect3" title="ADS Domains"><div class="titlepage"><div><div><h4 class="title"><a name="id372596"></a>ADS Domains</h4></div></div></div><p> 395 <a class="indexterm" name="id372603"></a> 396 <a class="indexterm" name="id372610"></a> 397 397 The procedure for joining an ADS domain is similar to the NT4 domain join, except the <code class="filename">smb.conf</code> file 398 398 will have the contents shown in <a class="link" href="idmapper.html#idmapadsdms" title="Example 14.2. ADS Domain Member Server smb.conf">ADS Domain Member Server smb.conf</a> 399 </p><div class="example"><a name="idmapadsdms"></a><p class="title"><b>Example 14.2. ADS Domain Member Server smb.conf</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id37 4511"></a><em class="parameter"><code>workgroup = BUTTERNET</code></em></td></tr><tr><td><a class="indexterm" name="id374523"></a><em class="parameter"><code>netbios name = GARGOYLE</code></em></td></tr><tr><td><a class="indexterm" name="id374534"></a><em class="parameter"><code>realm = BUTTERNET.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id374546"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id374557"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id374569"></a><em class="parameter"><code>idmap uid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id374580"></a><em class="parameter"><code>idmap gid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id374592"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id374604"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id374615"></a><em class="parameter"><code>printer admin = "BUTTERNET\Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>400 <a class="indexterm" name="id37 4630"></a>401 <a class="indexterm" name="id37 4637"></a>402 <a class="indexterm" name="id37 4644"></a>403 <a class="indexterm" name="id37 4651"></a>404 <a class="indexterm" name="id37 4657"></a>405 <a class="indexterm" name="id37 4664"></a>406 <a class="indexterm" name="id37 4671"></a>399 </p><div class="example"><a name="idmapadsdms"></a><p class="title"><b>Example 14.2. ADS Domain Member Server smb.conf</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id372660"></a><em class="parameter"><code>workgroup = BUTTERNET</code></em></td></tr><tr><td><a class="indexterm" name="id372672"></a><em class="parameter"><code>netbios name = GARGOYLE</code></em></td></tr><tr><td><a class="indexterm" name="id372683"></a><em class="parameter"><code>realm = BUTTERNET.BIZ</code></em></td></tr><tr><td><a class="indexterm" name="id372694"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id372706"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id372718"></a><em class="parameter"><code>idmap uid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id372729"></a><em class="parameter"><code>idmap gid = 500-10000000</code></em></td></tr><tr><td><a class="indexterm" name="id372741"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id372752"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id372764"></a><em class="parameter"><code>printer admin = "BUTTERNET\Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p> 400 <a class="indexterm" name="id372779"></a> 401 <a class="indexterm" name="id372786"></a> 402 <a class="indexterm" name="id372793"></a> 403 <a class="indexterm" name="id372800"></a> 404 <a class="indexterm" name="id372806"></a> 405 <a class="indexterm" name="id372813"></a> 406 <a class="indexterm" name="id372820"></a> 407 407 ADS DMS operation requires use of kerberos (KRB). For this to work, the <code class="filename">krb5.conf</code> 408 408 must be configured. The exact requirements depends on which version of MIT or Heimdal Kerberos is being … … 417 417 </p></li><li class="step" title="Step 3"><p> 418 418 Execute: 419 <a class="indexterm" name="id37 4725"></a>419 <a class="indexterm" name="id372874"></a> 420 420 </p><pre class="screen"> 421 421 <code class="prompt">root# </code> net ads join -UAdministrator%password … … 437 437 Join to domain is not valid 438 438 </pre><p> 439 <a class="indexterm" name="id37 4778"></a>440 <a class="indexterm" name="id37 4784"></a>441 <a class="indexterm" name="id37 4791"></a>442 <a class="indexterm" name="id37 4798"></a>439 <a class="indexterm" name="id372926"></a> 440 <a class="indexterm" name="id372933"></a> 441 <a class="indexterm" name="id372940"></a> 442 <a class="indexterm" name="id372947"></a> 443 443 The specific error message may differ from the above because it depends on the type of failure that 444 444 may have occurred. Increase the <em class="parameter"><code>log level</code></em> to 10, repeat the test, … … 446 446 </p></li><li class="step" title="Step 4"><p> 447 447 Start the <code class="literal">nmbd</code>, <code class="literal">winbind</code>, and <code class="literal">smbd</code> daemons in the order shown. 448 </p></li></ol></div></div></div><div class="sect2" title="IDMAP_RID with Winbind"><div class="titlepage"><div><div><h3 class="title"><a name="id37 4842"></a>IDMAP_RID with Winbind</h3></div></div></div><p>449 <a class="indexterm" name="id37 4850"></a>450 <a class="indexterm" name="id37 4856"></a>451 <a class="indexterm" name="id37 4863"></a>452 <a class="indexterm" name="id37 4869"></a>448 </p></li></ol></div></div></div><div class="sect2" title="IDMAP_RID with Winbind"><div class="titlepage"><div><div><h3 class="title"><a name="id372991"></a>IDMAP_RID with Winbind</h3></div></div></div><p> 449 <a class="indexterm" name="id372998"></a> 450 <a class="indexterm" name="id373005"></a> 451 <a class="indexterm" name="id373012"></a> 452 <a class="indexterm" name="id373018"></a> 453 453 The <code class="literal">idmap_rid</code> facility is a new tool that, unlike native winbind, creates a 454 454 predictable mapping of MS Windows SIDs to UNIX UIDs and GIDs. The key benefit of this method … … 457 457 is not compatible with trusted domain implementations. 458 458 </p><p> 459 <a class="indexterm" name="id37 4889"></a>460 <a class="indexterm" name="id37 4895"></a>461 <a class="indexterm" name="id37 4902"></a>462 <a class="indexterm" name="id37 4909"></a>459 <a class="indexterm" name="id373038"></a> 460 <a class="indexterm" name="id373044"></a> 461 <a class="indexterm" name="id373051"></a> 462 <a class="indexterm" name="id373058"></a> 463 463 This alternate method of SID to UID/GID mapping can be achieved using the idmap_rid 464 464 plug-in. This plug-in uses the RID of the user SID to derive the UID and GID by adding the … … 468 468 <em class="parameter"><code>idmap gid</code></em> ranges must be specified. 469 469 </p><p> 470 <a class="indexterm" name="id37 4938"></a>471 <a class="indexterm" name="id37 4945"></a>470 <a class="indexterm" name="id373087"></a> 471 <a class="indexterm" name="id373094"></a> 472 472 The idmap_rid facility can be used both for NT4/Samba-style domains and Active Directory. 473 473 To use this with an NT4 domain, do not include the <em class="parameter"><code>realm</code></em> parameter; additionally, the … … 476 476 An example <code class="filename">smb.conf</code> file for and ADS domain environment is shown in <a class="link" href="idmapper.html#idmapadsridDMS" title="Example 14.3. ADS Domain Member smb.conf using idmap_rid">ADS 477 477 Domain Member smb.conf using idmap_rid</a>. 478 </p><div class="example"><a name="idmapadsridDMS"></a><p class="title"><b>Example 14.3. ADS Domain Member smb.conf using idmap_rid</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id37 5009"></a><em class="parameter"><code>workgroup = KPAK</code></em></td></tr><tr><td><a class="indexterm" name="id375020"></a><em class="parameter"><code>netbios name = BIGJOE</code></em></td></tr><tr><td><a class="indexterm" name="id375032"></a><em class="parameter"><code>realm = CORP.KPAK.COM</code></em></td></tr><tr><td><a class="indexterm" name="id375043"></a><em class="parameter"><code>server string = Office Server</code></em></td></tr><tr><td><a class="indexterm" name="id375055"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id375066"></a><em class="parameter"><code>allow trusted domains = No</code></em></td></tr><tr><td><a class="indexterm" name="id375078"></a><em class="parameter"><code>idmap backend = idmap_rid:KPAK=500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id375090"></a><em class="parameter"><code>idmap uid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id375101"></a><em class="parameter"><code>idmap gid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id375113"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id375125"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id375136"></a><em class="parameter"><code>winbind enum users = No</code></em></td></tr><tr><td><a class="indexterm" name="id375148"></a><em class="parameter"><code>winbind enum groups = No</code></em></td></tr><tr><td><a class="indexterm" name="id375159"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id375171"></a><em class="parameter"><code>printer admin = "Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p>479 <a class="indexterm" name="id37 5186"></a>480 <a class="indexterm" name="id37 5193"></a>481 <a class="indexterm" name="id37 5199"></a>482 <a class="indexterm" name="id37 5206"></a>478 </p><div class="example"><a name="idmapadsridDMS"></a><p class="title"><b>Example 14.3. ADS Domain Member smb.conf using idmap_rid</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id373158"></a><em class="parameter"><code>workgroup = KPAK</code></em></td></tr><tr><td><a class="indexterm" name="id373169"></a><em class="parameter"><code>netbios name = BIGJOE</code></em></td></tr><tr><td><a class="indexterm" name="id373181"></a><em class="parameter"><code>realm = CORP.KPAK.COM</code></em></td></tr><tr><td><a class="indexterm" name="id373192"></a><em class="parameter"><code>server string = Office Server</code></em></td></tr><tr><td><a class="indexterm" name="id373204"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id373215"></a><em class="parameter"><code>allow trusted domains = No</code></em></td></tr><tr><td><a class="indexterm" name="id373227"></a><em class="parameter"><code>idmap backend = idmap_rid:KPAK=500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id373239"></a><em class="parameter"><code>idmap uid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id373250"></a><em class="parameter"><code>idmap gid = 500-100000000</code></em></td></tr><tr><td><a class="indexterm" name="id373262"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id373273"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id373285"></a><em class="parameter"><code>winbind enum users = No</code></em></td></tr><tr><td><a class="indexterm" name="id373297"></a><em class="parameter"><code>winbind enum groups = No</code></em></td></tr><tr><td><a class="indexterm" name="id373308"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id373320"></a><em class="parameter"><code>printer admin = "Domain Admins"</code></em></td></tr></table></div></div><br class="example-break"><p> 479 <a class="indexterm" name="id373335"></a> 480 <a class="indexterm" name="id373341"></a> 481 <a class="indexterm" name="id373348"></a> 482 <a class="indexterm" name="id373355"></a> 483 483 In a large domain with many users it is imperative to disable enumeration of users and groups. 484 484 For example, at a site that has 22,000 users in Active Directory the winbind-based user and … … 489 489 commands. It will be possible to perform the lookup for individual users, as shown in the following procedure. 490 490 </p><p> 491 <a class="indexterm" name="id37 5239"></a>492 <a class="indexterm" name="id37 5245"></a>491 <a class="indexterm" name="id373388"></a> 492 <a class="indexterm" name="id373394"></a> 493 493 The use of this tool requires configuration of NSS as per the native use of winbind. Edit the 494 494 <code class="filename">/etc/nsswitch.conf</code> so it has the following parameters: … … 516 516 </pre><p> 517 517 </p><p> 518 <a class="indexterm" name="id37 5320"></a>518 <a class="indexterm" name="id373469"></a> 519 519 An invalid or failed join can be detected by executing: 520 520 </p><pre class="screen"> … … 532 532 </p></li><li class="step" title="Step 5"><p> 533 533 Validate the operation of this configuration by executing: 534 <a class="indexterm" name="id37 5380"></a>534 <a class="indexterm" name="id373529"></a> 535 535 </p><pre class="screen"> 536 536 <code class="prompt">root# </code> getent passwd administrator 537 537 administrator:x:1000:1013:Administrator:/home/BE/administrator:/bin/bash 538 538 </pre><p> 539 </p></li></ol></div></div><div class="sect2" title="IDMAP Storage in LDAP Using Winbind"><div class="titlepage"><div><div><h3 class="title"><a name="id37 5401"></a>IDMAP Storage in LDAP Using Winbind</h3></div></div></div><p>540 <a class="indexterm" name="id37 5409"></a>541 <a class="indexterm" name="id37 5415"></a>539 </p></li></ol></div></div><div class="sect2" title="IDMAP Storage in LDAP Using Winbind"><div class="titlepage"><div><div><h3 class="title"><a name="id373550"></a>IDMAP Storage in LDAP Using Winbind</h3></div></div></div><p> 540 <a class="indexterm" name="id373557"></a> 541 <a class="indexterm" name="id373564"></a> 542 542 The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains and 543 543 ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any … … 548 548 An example is for an ADS domain is shown in <a class="link" href="idmapper.html#idmapldapDMS" title="Example 14.4. ADS Domain Member Server using LDAP">ADS Domain Member Server using 549 549 LDAP</a>. 550 </p><div class="example"><a name="idmapldapDMS"></a><p class="title"><b>Example 14.4. ADS Domain Member Server using LDAP</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id37 5464"></a><em class="parameter"><code>workgroup = SNOWSHOW</code></em></td></tr><tr><td><a class="indexterm" name="id375476"></a><em class="parameter"><code>netbios name = GOODELF</code></em></td></tr><tr><td><a class="indexterm" name="id375487"></a><em class="parameter"><code>realm = SNOWSHOW.COM</code></em></td></tr><tr><td><a class="indexterm" name="id375499"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id375510"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id375522"></a><em class="parameter"><code>log level = 1 ads:10 auth:10 sam:10 rpc:10</code></em></td></tr><tr><td><a class="indexterm" name="id375534"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id375545"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id375557"></a><em class="parameter"><code>ldap suffix = dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id375569"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap.snowshow.com</code></em></td></tr><tr><td><a class="indexterm" name="id375580"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id375592"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id375604"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id375615"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>551 <a class="indexterm" name="id37 5630"></a>550 </p><div class="example"><a name="idmapldapDMS"></a><p class="title"><b>Example 14.4. ADS Domain Member Server using LDAP</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id373613"></a><em class="parameter"><code>workgroup = SNOWSHOW</code></em></td></tr><tr><td><a class="indexterm" name="id373624"></a><em class="parameter"><code>netbios name = GOODELF</code></em></td></tr><tr><td><a class="indexterm" name="id373636"></a><em class="parameter"><code>realm = SNOWSHOW.COM</code></em></td></tr><tr><td><a class="indexterm" name="id373647"></a><em class="parameter"><code>server string = Samba Server</code></em></td></tr><tr><td><a class="indexterm" name="id373659"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id373670"></a><em class="parameter"><code>log level = 1 ads:10 auth:10 sam:10 rpc:10</code></em></td></tr><tr><td><a class="indexterm" name="id373682"></a><em class="parameter"><code>ldap admin dn = cn=Manager,dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id373694"></a><em class="parameter"><code>ldap idmap suffix = ou=Idmap</code></em></td></tr><tr><td><a class="indexterm" name="id373705"></a><em class="parameter"><code>ldap suffix = dc=SNOWSHOW,dc=COM</code></em></td></tr><tr><td><a class="indexterm" name="id373717"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap.snowshow.com</code></em></td></tr><tr><td><a class="indexterm" name="id373729"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id373740"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id373752"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id373764"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr></table></div></div><br class="example-break"><p> 551 <a class="indexterm" name="id373778"></a> 552 552 In the case of an NT4 or Samba-3-style domain the <em class="parameter"><code>realm</code></em> is not used, and the 553 553 command used to join the domain is <code class="literal">net rpc join</code>. The above example also demonstrates 554 554 advanced error-reporting techniques that are documented in <a class="link" href="bugreport.html#dbglvl" title="Debug Levels">Reporting Bugs</a>. 555 555 </p><p> 556 <a class="indexterm" name="id37 5662"></a>557 <a class="indexterm" name="id37 5669"></a>558 <a class="indexterm" name="id37 5675"></a>556 <a class="indexterm" name="id373810"></a> 557 <a class="indexterm" name="id373817"></a> 558 <a class="indexterm" name="id373824"></a> 559 559 Where MIT kerberos is installed (version 1.3.4 or later), edit the <code class="filename">/etc/krb5.conf</code> 560 560 file so it has the following contents: … … 611 611 </pre><p> 612 612 </p><p> 613 <a class="indexterm" name="id37 5748"></a>614 <a class="indexterm" name="id37 5754"></a>613 <a class="indexterm" name="id373896"></a> 614 <a class="indexterm" name="id373903"></a> 615 615 You will need the <a class="ulink" href="http://www.padl.com" target="_top">PADL</a> <code class="literal">nss_ldap</code> 616 616 tool set for this solution. Configure the <code class="filename">/etc/ldap.conf</code> file so it has … … 675 675 Start the <code class="literal">nmbd</code>, <code class="literal">winbind</code>, and <code class="literal">smbd</code> daemons in the order shown. 676 676 </p></li></ol></div><p> 677 <a class="indexterm" name="id37 5936"></a>677 <a class="indexterm" name="id374084"></a> 678 678 Follow the diagnositic procedures shown earlier in this chapter to identify success or failure of the join. 679 679 In many cases a failure is indicated by a silent return to the command prompt with no indication of the 680 680 reason for failure. 681 </p></div><div class="sect2" title="IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension"><div class="titlepage"><div><div><h3 class="title"><a name="id37 5947"></a>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</h3></div></div></div><p>682 <a class="indexterm" name="id37 5955"></a>683 <a class="indexterm" name="id37 5962"></a>681 </p></div><div class="sect2" title="IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension"><div class="titlepage"><div><div><h3 class="title"><a name="id374095"></a>IDMAP and NSS Using LDAP from ADS with RFC2307bis Schema Extension</h3></div></div></div><p> 682 <a class="indexterm" name="id374104"></a> 683 <a class="indexterm" name="id374110"></a> 684 684 The use of this method is messy. The information provided in the following is for guidance only 685 685 and is very definitely not complete. This method does work; it is used in a number of large sites … … 688 688 An example <code class="filename">smb.conf</code> file is shown in <a class="link" href="idmapper.html#idmaprfc2307" title="Example 14.5. ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS">ADS Domain Member Server using 689 689 RFC2307bis Schema Extension Date via NSS</a>. 690 </p><div class="example"><a name="idmaprfc2307"></a><p class="title"><b>Example 14.5. ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id37 6017"></a><em class="parameter"><code>workgroup = BOBBY</code></em></td></tr><tr><td><a class="indexterm" name="id376029"></a><em class="parameter"><code>realm = BOBBY.COM</code></em></td></tr><tr><td><a class="indexterm" name="id376040"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id376052"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id376063"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id376075"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id376087"></a><em class="parameter"><code>winbind cache time = 5</code></em></td></tr><tr><td><a class="indexterm" name="id376098"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id376110"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id376122"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr></table></div></div><br class="example-break"><p>691 <a class="indexterm" name="id37 6136"></a>690 </p><div class="example"><a name="idmaprfc2307"></a><p class="title"><b>Example 14.5. ADS Domain Member Server using RFC2307bis Schema Extension Date via NSS</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td># Global parameters</td></tr><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id374165"></a><em class="parameter"><code>workgroup = BOBBY</code></em></td></tr><tr><td><a class="indexterm" name="id374176"></a><em class="parameter"><code>realm = BOBBY.COM</code></em></td></tr><tr><td><a class="indexterm" name="id374188"></a><em class="parameter"><code>security = ADS</code></em></td></tr><tr><td><a class="indexterm" name="id374199"></a><em class="parameter"><code>idmap uid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id374211"></a><em class="parameter"><code>idmap gid = 150000-550000</code></em></td></tr><tr><td><a class="indexterm" name="id374222"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr><tr><td><a class="indexterm" name="id374234"></a><em class="parameter"><code>winbind cache time = 5</code></em></td></tr><tr><td><a class="indexterm" name="id374246"></a><em class="parameter"><code>winbind use default domain = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id374257"></a><em class="parameter"><code>winbind trusted domains only = Yes</code></em></td></tr><tr><td><a class="indexterm" name="id374269"></a><em class="parameter"><code>winbind nested groups = Yes</code></em></td></tr></table></div></div><br class="example-break"><p> 691 <a class="indexterm" name="id374284"></a> 692 692 The DMS must be joined to the domain using the usual procedure. Additionally, it is necessary 693 693 to build and install the PADL nss_ldap tool set. Be sure to build this tool set with the … … 698 698 </pre><p> 699 699 </p><p> 700 <a class="indexterm" name="id37 6154"></a>700 <a class="indexterm" name="id374302"></a> 701 701 The following <code class="filename">/etc/nsswitch.conf</code> file contents are required: 702 702 </p><pre class="screen"> … … 710 710 </pre><p> 711 711 </p><p> 712 <a class="indexterm" name="id37 6177"></a>713 <a class="indexterm" name="id37 6184"></a>712 <a class="indexterm" name="id374325"></a> 713 <a class="indexterm" name="id374332"></a> 714 714 The <code class="filename">/etc/ldap.conf</code> file must be configured also. Refer to the PADL documentation 715 715 and source code for nss_ldap to specific instructions. … … 717 717 The next step involves preparation of the ADS schema. This is briefly discussed in the remaining 718 718 part of this chapter. 719 </p><div class="sect3" title="IDMAP, Active Directory, and MS Services for UNIX 3.5"><div class="titlepage"><div><div><h4 class="title"><a name="id37 6203"></a>IDMAP, Active Directory, and MS Services for UNIX 3.5</h4></div></div></div><p>720 <a class="indexterm" name="id37 6211"></a>719 </p><div class="sect3" title="IDMAP, Active Directory, and MS Services for UNIX 3.5"><div class="titlepage"><div><div><h4 class="title"><a name="id374351"></a>IDMAP, Active Directory, and MS Services for UNIX 3.5</h4></div></div></div><p> 720 <a class="indexterm" name="id374359"></a> 721 721 The Microsoft Windows Service for UNIX (SFU) version 3.5 is available for free 722 722 <a class="ulink" href="http://www.microsoft.com/windows/sfu/" target="_top">download</a> 723 723 from the Microsoft Web site. You will need to download this tool and install it following 724 724 Microsoft instructions. 725 </p></div><div class="sect3" title="IDMAP, Active Directory and AD4UNIX"><div class="titlepage"><div><div><h4 class="title"><a name="id37 6228"></a>IDMAP, Active Directory and AD4UNIX</h4></div></div></div><p>725 </p></div><div class="sect3" title="IDMAP, Active Directory and AD4UNIX"><div class="titlepage"><div><div><h4 class="title"><a name="id374376"></a>IDMAP, Active Directory and AD4UNIX</h4></div></div></div><p> 726 726 Instructions for obtaining and installing the AD4UNIX tool set can be found from the 727 727 <a class="ulink" href="http://www.geekcomix.com/cgi-bin/classnotes/wiki.pl?LDAP01/An_Alternative_Approach" target="_top"> 728 728 Geekcomix</a> Web site. 729 </p></div></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id37 2743" href="#id372743" class="para">4</a>] </sup>Samba local account mode results in both729 </p></div></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id370893" href="#id370893" class="para">4</a>] </sup>Samba local account mode results in both 730 730 <code class="literal">DOMINICUS\FJones</code> and <code class="literal">FRANCISCUS\FJones</code> mapping to the UNIX user 731 731 <code class="literal">FJones</code>.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NetCommand.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="rights.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 13. Remote and Local Management: The Net Command </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 15. User Rights and Privileges</td></tr></table></div></body></html>
Note:
See TracChangeset
for help on using the changeset viewer.
