- Timestamp:
- Jun 17, 2009, 2:19:52 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/Samba3-HOWTO/groupmapping.html
r218 r274 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 12. Group Mapping: MS Windows and UNIX</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3. 2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="passdb.html" title="Chapter 11. Account Information Databases"><link rel="next" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command"></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 12. Group Mapping: MS Windows and UNIX</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="passdb.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="NetCommand.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter 12. Group Mapping: MS Windows and UNIX</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</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 class="author"><h3 class="author"><span class="firstname">Jean François</span> <span class="surname">Micouleau</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@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="groupmapping.html#id2595838">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596254">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596591">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596648">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597232">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597472">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598097">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598174">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598186">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598357">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598485">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598497">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598584">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></div><p>2 <a class="indexterm" name="id25957 12"></a>3 <a class="indexterm" name="id25957 21"></a>4 <a class="indexterm" name="id25957 28"></a>5 <a class="indexterm" name="id25957 35"></a>6 <a class="indexterm" name="id25957 41"></a>7 <a class="indexterm" name="id2595 748"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 12. Group Mapping: MS Windows and UNIX</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.3.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="passdb.html" title="Chapter 11. Account Information Databases"><link rel="next" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command"></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 12. Group Mapping: MS Windows and UNIX</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="passdb.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="NetCommand.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="groupmapping"></a>Chapter 12. Group Mapping: MS Windows and UNIX</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</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 class="author"><h3 class="author"><span class="firstname">Jean François</span> <span class="surname">Micouleau</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@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="groupmapping.html#id2595891">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="groupmapping.html#id2596307">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2596644">Warning: User Private Group Problems</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2596701">Nested Groups: Adding Windows Domain Groups to Windows Local Groups</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597277">Important Administrative Information</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2597518">Default Users, Groups, and Relative Identifiers</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598143">Example Configuration</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598220">Configuration Scripts</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598231">Sample smb.conf Add Group Script</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598403">Script to Configure Group Mapping</a></span></dt></dl></dd><dt><span class="sect1"><a href="groupmapping.html#id2598530">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="groupmapping.html#id2598543">Adding Groups Fails</a></span></dt><dt><span class="sect2"><a href="groupmapping.html#id2598630">Adding Domain Users to the Workstation Power Users Group</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id2595765"></a> 3 <a class="indexterm" name="id2595774"></a> 4 <a class="indexterm" name="id2595781"></a> 5 <a class="indexterm" name="id2595788"></a> 6 <a class="indexterm" name="id2595794"></a> 7 <a class="indexterm" name="id2595801"></a> 8 8 Starting with Samba-3, new group mapping functionality is available to create associations 9 9 between Windows group SIDs and UNIX group GIDs. The <code class="literal">groupmap</code> subcommand 10 10 included with the <span class="application">net</span> tool can be used to manage these associations. 11 11 </p><p> 12 <a class="indexterm" name="id2595 773"></a>13 <a class="indexterm" name="id2595 780"></a>12 <a class="indexterm" name="id2595826"></a> 13 <a class="indexterm" name="id2595833"></a> 14 14 The new facility for mapping NT groups to UNIX system groups allows the administrator to decide 15 15 which NT domain groups are to be exposed to MS Windows clients. Only those NT groups that map … … 17 17 in group selection lists in tools that access domain users and groups. 18 18 </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 19 <a class="indexterm" name="id25958 02"></a>20 <a class="indexterm" name="id25958 09"></a>19 <a class="indexterm" name="id2595855"></a> 20 <a class="indexterm" name="id2595862"></a> 21 21 The <em class="parameter"><code>domain admin group</code></em> parameter has been removed in Samba-3 and should no longer 22 22 be specified in <code class="filename">smb.conf</code>. In Samba-2.2.x, this parameter was used to give the listed users membership in the 23 23 <code class="constant">Domain Admins</code> Windows group, which gave local admin rights on their workstations 24 24 (in default configurations). 25 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id25958 38"></a>Features and Benefits</h2></div></div></div><p>25 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2595891"></a>Features and Benefits</h2></div></div></div><p> 26 26 Samba allows the administrator to create MS Windows NT4/200x group accounts and to 27 27 arbitrarily associate them with UNIX/Linux group accounts. 28 28 </p><p> 29 <a class="indexterm" name="id2595 852"></a>30 <a class="indexterm" name="id2595 858"></a>31 <a class="indexterm" name="id2595 865"></a>32 <a class="indexterm" name="id2595 872"></a>33 <a class="indexterm" name="id2595 878"></a>34 <a class="indexterm" name="id2595 885"></a>35 <a class="indexterm" name="id2595 892"></a>29 <a class="indexterm" name="id2595905"></a> 30 <a class="indexterm" name="id2595911"></a> 31 <a class="indexterm" name="id2595918"></a> 32 <a class="indexterm" name="id2595925"></a> 33 <a class="indexterm" name="id2595931"></a> 34 <a class="indexterm" name="id2595938"></a> 35 <a class="indexterm" name="id2595945"></a> 36 36 Group accounts can be managed using the MS Windows NT4 or MS Windows 200x/XP Professional MMC tools. 37 37 Appropriate interface scripts should be provided in <code class="filename">smb.conf</code> if it is desired that UNIX/Linux system … … 42 42 parameters in the <code class="filename">smb.conf</code> file. 43 43 </p><div class="figure"><a name="idmap-sid2gid"></a><p class="title"><b>Figure 12.1. IDMAP: Group SID-to-GID Resolution.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-sid2gid.png" width="270" alt="IDMAP: Group SID-to-GID Resolution."></div></div></div><br class="figure-break"><div class="figure"><a name="idmap-gid2sid"></a><p class="title"><b>Figure 12.2. IDMAP: GID Resolution to Matching SID.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-gid2sid.png" width="270" alt="IDMAP: GID Resolution to Matching SID."></div></div></div><br class="figure-break"><p> 44 <a class="indexterm" name="id25960 35"></a>45 <a class="indexterm" name="id25960 42"></a>46 <a class="indexterm" name="id2596 048"></a>47 <a class="indexterm" name="id2596 057"></a>44 <a class="indexterm" name="id2596088"></a> 45 <a class="indexterm" name="id2596095"></a> 46 <a class="indexterm" name="id2596101"></a> 47 <a class="indexterm" name="id2596110"></a> 48 48 In both cases, when winbindd is not running, only locally resolvable groups can be recognized. Please refer to 49 49 <a class="link" href="groupmapping.html#idmap-sid2gid" title="Figure 12.1. IDMAP: Group SID-to-GID Resolution.">IDMAP: Group SID-to-GID Resolution</a> and <a class="link" href="groupmapping.html#idmap-gid2sid" title="Figure 12.2. IDMAP: GID Resolution to Matching SID.">IDMAP: GID Resolution to Matching SID</a>. The <code class="literal">net groupmap</code> is … … 51 51 group mappings</a>. 52 52 </p><div class="figure"><a name="idmap-store-gid2sid"></a><p class="title"><b>Figure 12.3. IDMAP Storing Group Mappings.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-store-gid2sid.png" width="270" alt="IDMAP Storing Group Mappings."></div></div></div><br class="figure-break"><p> 53 <a class="indexterm" name="id25961 44"></a>54 <a class="indexterm" name="id2596 150"></a>55 <a class="indexterm" name="id2596 157"></a>56 <a class="indexterm" name="id2596 164"></a>53 <a class="indexterm" name="id2596196"></a> 54 <a class="indexterm" name="id2596203"></a> 55 <a class="indexterm" name="id2596210"></a> 56 <a class="indexterm" name="id2596217"></a> 57 57 Administrators should be aware that where <code class="filename">smb.conf</code> group interface scripts make 58 58 direct calls to the UNIX/Linux system tools (the shadow utilities, <code class="literal">groupadd</code>, … … 63 63 UNIX/Linux group, an attempt that will of course fail. 64 64 </p><p> 65 <a class="indexterm" name="id25962 12"></a>66 <a class="indexterm" name="id25962 18"></a>65 <a class="indexterm" name="id2596265"></a> 66 <a class="indexterm" name="id2596271"></a> 67 67 There are several possible workarounds for the operating system tools limitation. One 68 68 method is to use a script that generates a name for the UNIX/Linux system group that … … 70 70 back to the calling Samba interface. This will provide a dynamic workaround solution. 71 71 </p><p> 72 <a class="indexterm" name="id25962 34"></a>72 <a class="indexterm" name="id2596287"></a> 73 73 Another workaround is to manually create a UNIX/Linux group, then manually create the 74 74 MS Windows NT4/200x group on the Samba server, and then use the <code class="literal">net groupmap</code> 75 75 tool to connect the two to each other. 76 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2596 254"></a>Discussion</h2></div></div></div><p>77 <a class="indexterm" name="id2596 262"></a>78 <a class="indexterm" name="id2596 269"></a>76 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2596307"></a>Discussion</h2></div></div></div><p> 77 <a class="indexterm" name="id2596315"></a> 78 <a class="indexterm" name="id2596322"></a> 79 79 When you install <span class="application">MS Windows NT4/200x</span> on a computer, the installation 80 80 program creates default users and groups, notably the <code class="constant">Administrators</code> group, … … 83 83 local machine. 84 84 </p><p> 85 <a class="indexterm" name="id2596 294"></a>85 <a class="indexterm" name="id2596347"></a> 86 86 The <code class="constant">Administrator</code> user is a member of the <code class="constant">Administrators</code> group, and thus inherits 87 87 <code class="constant">Administrators</code> group privileges. If a <code class="constant">joe</code> user is created to be a member of the … … 89 89 <code class="constant">Administrator</code>. 90 90 </p><p> 91 <a class="indexterm" name="id25963 33"></a>92 <a class="indexterm" name="id25963 40"></a>93 <a class="indexterm" name="id2596 347"></a>94 <a class="indexterm" name="id2596 354"></a>91 <a class="indexterm" name="id2596386"></a> 92 <a class="indexterm" name="id2596393"></a> 93 <a class="indexterm" name="id2596400"></a> 94 <a class="indexterm" name="id2596406"></a> 95 95 When an MS Windows NT4/200x/XP machine is made a domain member, the “<span class="quote">Domain Admins</span>” group of the 96 96 PDC is added to the local <code class="constant">Administrators</code> group of the workstation. Every member of the … … 98 98 logging on the workstation. 99 99 </p><p> 100 <a class="indexterm" name="id2596 382"></a>101 <a class="indexterm" name="id2596 389"></a>100 <a class="indexterm" name="id2596435"></a> 101 <a class="indexterm" name="id2596442"></a> 102 102 The following steps describe how to make Samba PDC users members of the <code class="constant">Domain Admins</code> group. 103 103 </p><div class="orderedlist"><ol type="1"><li><p> 104 104 Create a UNIX group (usually in <code class="filename">/etc/group</code>); let's call it <code class="constant">domadm</code>. 105 105 </p></li><li><p> 106 <a class="indexterm" name="id25964 27"></a>106 <a class="indexterm" name="id2596480"></a> 107 107 Add to this group the users that must be “<span class="quote">Administrators</span>”. For example, 108 108 if you want <code class="constant">joe, john</code>, and <code class="constant">mary</code> to be administrators, … … 118 118 </pre><p> 119 119 </p><p> 120 <a class="indexterm" name="id2596 494"></a>120 <a class="indexterm" name="id2596547"></a> 121 121 The quotes around “<span class="quote">Domain Admins</span>” are necessary due to the space in the group name. 122 122 Also make sure to leave no white space surrounding the equal character (=). … … 124 124 Now <code class="constant">joe, john</code>, and <code class="constant">mary</code> are domain administrators. 125 125 </p><p> 126 <a class="indexterm" name="id25965 23"></a>126 <a class="indexterm" name="id2596576"></a> 127 127 It is possible to map any arbitrary UNIX group to any Windows NT4/200x group as well as 128 128 to make any UNIX group a Windows domain group. For example, if you wanted to include a … … 136 136 the space from being interpreted as a command delimiter. 137 137 </p><p> 138 <a class="indexterm" name="id2596 570"></a>139 <a class="indexterm" name="id2596 577"></a>138 <a class="indexterm" name="id2596623"></a> 139 <a class="indexterm" name="id2596630"></a> 140 140 Be aware that the RID parameter is an unsigned 32-bit integer that should 141 141 normally start at 1000. However, this RID must not overlap with any RID assigned … … 143 143 you are using. Future versions of the tools may perform the verification automatically, 144 144 but for now the burden is on you. 145 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596 591"></a>Warning: User Private Group Problems</h3></div></div></div><p>146 <a class="indexterm" name="id2596 599"></a>147 <a class="indexterm" name="id25966 06"></a>148 <a class="indexterm" name="id25966 13"></a>145 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596644"></a>Warning: User Private Group Problems</h3></div></div></div><p> 146 <a class="indexterm" name="id2596652"></a> 147 <a class="indexterm" name="id2596659"></a> 148 <a class="indexterm" name="id2596666"></a> 149 149 Windows does not permit user and group accounts to have the same name. 150 150 This has serious implications for all sites that use private group accounts. … … 153 153 of Linux, by default create private groups. 154 154 </p><p> 155 <a class="indexterm" name="id25966 29"></a>156 <a class="indexterm" name="id25966 36"></a>155 <a class="indexterm" name="id2596682"></a> 156 <a class="indexterm" name="id2596689"></a> 157 157 When mapping a UNIX/Linux group to a Windows group account, all conflict can 158 158 be avoided by assuring that the Windows domain group name does not overlap 159 159 with any user account name. 160 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596 648"></a>Nested Groups: Adding Windows Domain Groups to Windows Local Groups</h3></div></div></div><a class="indexterm" name="id2596655"></a><p>161 <a class="indexterm" name="id2596 666"></a>160 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2596701"></a>Nested Groups: Adding Windows Domain Groups to Windows Local Groups</h3></div></div></div><a class="indexterm" name="id2596708"></a><p> 161 <a class="indexterm" name="id2596719"></a> 162 162 This functionality is known as <code class="constant">nested groups</code> and was first added to 163 163 Samba-3.0.3. 164 164 </p><p> 165 <a class="indexterm" name="id2596 682"></a>165 <a class="indexterm" name="id2596734"></a> 166 166 All MS Windows products since the release of Windows NT 3.10 support the use of nested groups. 167 167 Many Windows network administrators depend on this capability because it greatly simplifies security 168 168 administration. 169 169 </p><p> 170 <a class="indexterm" name="id2596 695"></a>171 <a class="indexterm" name="id25967 02"></a>172 <a class="indexterm" name="id25967 09"></a>173 <a class="indexterm" name="id25967 16"></a>174 <a class="indexterm" name="id25967 23"></a>175 <a class="indexterm" name="id25967 30"></a>176 <a class="indexterm" name="id25967 37"></a>170 <a class="indexterm" name="id2596748"></a> 171 <a class="indexterm" name="id2596755"></a> 172 <a class="indexterm" name="id2596762"></a> 173 <a class="indexterm" name="id2596769"></a> 174 <a class="indexterm" name="id2596776"></a> 175 <a class="indexterm" name="id2596783"></a> 176 <a class="indexterm" name="id2596790"></a> 177 177 The nested group architecture was designed with the premise that day-to-day user and group membership 178 178 management should be performed on the domain security database. The application of group security … … 181 181 domain global groups and domain global users. 182 182 </p><p> 183 <a class="indexterm" name="id2596 755"></a>184 <a class="indexterm" name="id2596 762"></a>185 <a class="indexterm" name="id2596 769"></a>183 <a class="indexterm" name="id2596808"></a> 184 <a class="indexterm" name="id2596815"></a> 185 <a class="indexterm" name="id2596822"></a> 186 186 You may ask, What are the benefits of this arrangement? The answer is obvious to those who have plumbed 187 187 the dark depths of Windows networking architecture. Consider for a moment a server on which are stored … … 191 191 Answer: Account Unknown. 192 192 </p><p> 193 <a class="indexterm" name="id2596 789"></a>194 <a class="indexterm" name="id2596 796"></a>195 <a class="indexterm" name="id25968 03"></a>196 <a class="indexterm" name="id25968 09"></a>193 <a class="indexterm" name="id2596842"></a> 194 <a class="indexterm" name="id2596849"></a> 195 <a class="indexterm" name="id2596856"></a> 196 <a class="indexterm" name="id2596862"></a> 197 197 Unraveling the file ownership mess is an unenviable administrative task that can be avoided simply 198 198 by using local groups to control all file and directory access control. In this case, only the members … … 202 202 entries for domain global groups in the new domain that the server has been made a member of. 203 203 </p><p> 204 <a class="indexterm" name="id25968 40"></a>205 <a class="indexterm" name="id25968 47"></a>206 <a class="indexterm" name="id2596 854"></a>207 <a class="indexterm" name="id2596 861"></a>208 <a class="indexterm" name="id2596 868"></a>209 <a class="indexterm" name="id2596 875"></a>210 <a class="indexterm" name="id2596 882"></a>211 <a class="indexterm" name="id2596 889"></a>204 <a class="indexterm" name="id2596886"></a> 205 <a class="indexterm" name="id2596893"></a> 206 <a class="indexterm" name="id2596900"></a> 207 <a class="indexterm" name="id2596907"></a> 208 <a class="indexterm" name="id2596914"></a> 209 <a class="indexterm" name="id2596921"></a> 210 <a class="indexterm" name="id2596928"></a> 211 <a class="indexterm" name="id2596935"></a> 212 212 Another prominent example of the use of nested groups involves implementation of administrative privileges 213 213 on domain member workstations and servers. Administrative privileges are given to all members of the … … 218 218 privileges on each domain member. 219 219 </p><p> 220 <a class="indexterm" name="id25969 17"></a>221 <a class="indexterm" name="id25969 24"></a>222 <a class="indexterm" name="id25969 31"></a>223 <a class="indexterm" name="id25969 38"></a>220 <a class="indexterm" name="id2596963"></a> 221 <a class="indexterm" name="id2596970"></a> 222 <a class="indexterm" name="id2596976"></a> 223 <a class="indexterm" name="id2596983"></a> 224 224 UNIX/Linux has no concept of support for nested groups, and thus Samba has for a long time not supported 225 225 them either. The problem is that you would have to enter UNIX groups as auxiliary members of a group in … … 229 229 controller that the Samba server is a member of. 230 230 </p><p> 231 <a class="indexterm" name="id259 6968"></a>232 <a class="indexterm" name="id259 6975"></a>233 <a class="indexterm" name="id259 6982"></a>234 <a class="indexterm" name="id259 6989"></a>235 <a class="indexterm" name="id259 6996"></a>231 <a class="indexterm" name="id2597014"></a> 232 <a class="indexterm" name="id2597021"></a> 233 <a class="indexterm" name="id2597028"></a> 234 <a class="indexterm" name="id2597034"></a> 235 <a class="indexterm" name="id2597041"></a> 236 236 In effect, Samba supplements the <code class="filename">/etc/group</code> data via the dynamic 237 237 <code class="literal">libnss_winbind</code> mechanism. Beginning with Samba-3.0.3, this facility is used to provide … … 243 243 UNIX/Linux group <code class="constant">demo</code>. 244 244 </p><p> 245 <a class="indexterm" name="id25970 42"></a>246 <a class="indexterm" name="id25970 49"></a>247 <a class="indexterm" name="id2597 056"></a>248 <a class="indexterm" name="id2597 062"></a>249 <a class="indexterm" name="id2597 069"></a>250 <a class="indexterm" name="id2597 076"></a>251 <a class="indexterm" name="id2597 083"></a>245 <a class="indexterm" name="id2597088"></a> 246 <a class="indexterm" name="id2597095"></a> 247 <a class="indexterm" name="id2597101"></a> 248 <a class="indexterm" name="id2597108"></a> 249 <a class="indexterm" name="id2597115"></a> 250 <a class="indexterm" name="id2597122"></a> 251 <a class="indexterm" name="id2597129"></a> 252 252 To enable the use of nested groups, <code class="literal">winbindd</code> must be used with NSS winbind. 253 253 Creation and administration of the local groups is done best via the Windows Domain User Manager or its … … 257 257 <code class="prompt">root# </code> net rpc group add demo -L -Uroot%not24get 258 258 </pre><p> 259 <a class="indexterm" name="id25971 26"></a>260 <a class="indexterm" name="id25971 33"></a>259 <a class="indexterm" name="id2597172"></a> 260 <a class="indexterm" name="id2597179"></a> 261 261 Here the -L switch means that you want to create a local group. It may be necessary to add -S and -U 262 262 switches for accessing the correct host with appropriate user or root privileges. Adding and removing … … 267 267 net rpc group addmem demo "DOM\Domain Users" 268 268 </pre><p> 269 <a class="indexterm" name="id2597 173"></a>270 <a class="indexterm" name="id2597 180"></a>271 <a class="indexterm" name="id2597 187"></a>272 <a class="indexterm" name="id2597 194"></a>269 <a class="indexterm" name="id2597219"></a> 270 <a class="indexterm" name="id2597226"></a> 271 <a class="indexterm" name="id2597232"></a> 272 <a class="indexterm" name="id2597239"></a> 273 273 Having completed these two steps, the execution of <code class="literal">getent group demo</code> will show demo 274 274 members of the global <code class="constant">Domain Users</code> group as members of the group … … 278 278 added to the <code class="constant">demo</code> group now have the same local access permissions as local domain 279 279 users have. 280 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id25972 32"></a>Important Administrative Information</h3></div></div></div><p>280 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597277"></a>Important Administrative Information</h3></div></div></div><p> 281 281 Administrative rights are necessary in two specific forms: 282 282 </p><div class="orderedlist"><ol type="1"><li><p>For Samba-3 domain controllers and domain member servers/clients.</p></li><li><p>To manage domain member Windows workstations.</p></li></ol></div><p> 283 <a class="indexterm" name="id2597 263"></a>284 <a class="indexterm" name="id2597 270"></a>285 <a class="indexterm" name="id2597 277"></a>283 <a class="indexterm" name="id2597308"></a> 284 <a class="indexterm" name="id2597316"></a> 285 <a class="indexterm" name="id2597323"></a> 286 286 Versions of Samba up to and including 3.0.10 do not provide a means for assigning rights and privileges 287 287 that are necessary for system administration tasks from a Windows domain member client machine, so … … 289 289 managing workstation domain membership accounts, can be handled by any account other than root. 290 290 </p><p> 291 <a class="indexterm" name="id2597 294"></a>292 <a class="indexterm" name="id25973 01"></a>293 <a class="indexterm" name="id25973 08"></a>291 <a class="indexterm" name="id2597340"></a> 292 <a class="indexterm" name="id2597347"></a> 293 <a class="indexterm" name="id2597354"></a> 294 294 Samba-3.0.11 introduced a new privilege management interface (see <a class="link" href="rights.html" title="Chapter 15. User Rights and Privileges">User Rights and Privileges</a>) 295 295 that permits these tasks to be delegated to non-root (i.e., accounts other than the equivalent of the 296 296 MS Windows Administrator) accounts. 297 297 </p><p> 298 <a class="indexterm" name="id25973 29"></a>299 <a class="indexterm" name="id25973 36"></a>298 <a class="indexterm" name="id2597375"></a> 299 <a class="indexterm" name="id2597381"></a> 300 300 Administrative tasks on a Windows domain member workstation can be done by anyone who is a member of the 301 301 <code class="constant">Domain Admins</code> group. This group can be mapped to any convenient UNIX group. 302 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id25973 50"></a>Applicable Only to Versions Earlier than 3.0.11</h4></div></div></div><p>303 <a class="indexterm" name="id2597 359"></a>302 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2597396"></a>Applicable Only to Versions Earlier than 3.0.11</h4></div></div></div><p> 303 <a class="indexterm" name="id2597405"></a> 304 304 Administrative tasks on UNIX/Linux systems, such as adding users or groups, requires 305 305 <code class="constant">root</code>-level privilege. The addition of a Windows client to a Samba domain involves the 306 306 addition of a user account for the Windows client. 307 307 </p><p> 308 <a class="indexterm" name="id2597 376"></a>309 <a class="indexterm" name="id2597 383"></a>308 <a class="indexterm" name="id2597422"></a> 309 <a class="indexterm" name="id2597429"></a> 310 310 Many UNIX administrators continue to request that the Samba Team make it possible to add Windows workstations, or 311 311 the ability to add, delete, or modify user accounts, without requiring <code class="constant">root</code> privileges. 312 312 Such a request violates every understanding of basic UNIX system security. 313 313 </p><p> 314 <a class="indexterm" name="id25974 02"></a>315 <a class="indexterm" name="id25974 08"></a>316 <a class="indexterm" name="id25974 15"></a>317 <a class="indexterm" name="id25974 22"></a>318 <a class="indexterm" name="id25974 29"></a>319 <a class="indexterm" name="id25974 36"></a>314 <a class="indexterm" name="id2597447"></a> 315 <a class="indexterm" name="id2597454"></a> 316 <a class="indexterm" name="id2597461"></a> 317 <a class="indexterm" name="id2597468"></a> 318 <a class="indexterm" name="id2597475"></a> 319 <a class="indexterm" name="id2597482"></a> 320 320 There is no safe way to provide access on a UNIX/Linux system without providing 321 321 <code class="constant">root</code>-level privileges. Provision of <code class="constant">root</code> privileges can be done … … 325 325 accounts as well as domain member server and client accounts. This level of privilege is also needed to manage 326 326 share-level ACLs. 327 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597 472"></a>Default Users, Groups, and Relative Identifiers</h3></div></div></div><p>328 <a class="indexterm" name="id2597 481"></a>329 <a class="indexterm" name="id2597 490"></a>330 <a class="indexterm" name="id2597 496"></a>331 <a class="indexterm" name="id25975 03"></a>332 <a class="indexterm" name="id25975 10"></a>333 <a class="indexterm" name="id25975 17"></a>334 <a class="indexterm" name="id25975 24"></a>335 <a class="indexterm" name="id25975 31"></a>327 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2597518"></a>Default Users, Groups, and Relative Identifiers</h3></div></div></div><p> 328 <a class="indexterm" name="id2597526"></a> 329 <a class="indexterm" name="id2597535"></a> 330 <a class="indexterm" name="id2597542"></a> 331 <a class="indexterm" name="id2597549"></a> 332 <a class="indexterm" name="id2597556"></a> 333 <a class="indexterm" name="id2597563"></a> 334 <a class="indexterm" name="id2597570"></a> 335 <a class="indexterm" name="id2597576"></a> 336 336 When first installed, Windows NT4/200x/XP are preconfigured with certain user, group, and 337 337 alias entities. Each has a well-known RID. These must be preserved for continued … … 341 341 (provision) the default NT groups. 342 342 </p><p> 343 <a class="indexterm" name="id25975 52"></a>344 <a class="indexterm" name="id2597 559"></a>345 <a class="indexterm" name="id2597 566"></a>346 <a class="indexterm" name="id2597 573"></a>343 <a class="indexterm" name="id2597598"></a> 344 <a class="indexterm" name="id2597605"></a> 345 <a class="indexterm" name="id2597612"></a> 346 <a class="indexterm" name="id2597619"></a> 347 347 Each essential domain group must be assigned its respective well-known RID. The default users, groups, 348 348 aliases, and RIDs are shown in <a class="link" href="groupmapping.html#WKURIDS" title="Table 12.1. Well-Known User Default RIDs">Well-Known User Default RIDs</a>. 349 349 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 350 <a class="indexterm" name="id2597 595"></a>351 <a class="indexterm" name="id25976 01"></a>352 <a class="indexterm" name="id25976 08"></a>353 <a class="indexterm" name="id25976 15"></a>354 <a class="indexterm" name="id25976 22"></a>350 <a class="indexterm" name="id2597640"></a> 351 <a class="indexterm" name="id2597647"></a> 352 <a class="indexterm" name="id2597654"></a> 353 <a class="indexterm" name="id2597661"></a> 354 <a class="indexterm" name="id2597668"></a> 355 355 It is the administrator's responsibility to create the essential domain groups and to assign each 356 356 its default RID. 357 357 </p></div><p> 358 <a class="indexterm" name="id25976 34"></a>359 <a class="indexterm" name="id25976 41"></a>358 <a class="indexterm" name="id2597680"></a> 359 <a class="indexterm" name="id2597686"></a> 360 360 It is permissible to create any domain group that may be necessary; just make certain that the essential 361 361 domain groups (well known) have been created and assigned their default RIDs. Other groups you create may … … 366 366 </p><p> 367 367 </p><div class="table"><a name="WKURIDS"></a><p class="title"><b>Table 12.1. Well-Known User Default RIDs</b></p><div class="table-contents"><table summary="Well-Known User Default RIDs" border="1"><colgroup><col align="left"><col align="left"><col align="left"><col align="center"></colgroup><thead><tr><th align="left">Well-Known Entity</th><th align="left">RID</th><th align="left">Type</th><th align="center">Essential</th></tr></thead><tbody><tr><td align="left">Domain Administrator</td><td align="left">500</td><td align="left">User</td><td align="center">No</td></tr><tr><td align="left">Domain Guest</td><td align="left">501</td><td align="left">User</td><td align="center">No</td></tr><tr><td align="left">Domain KRBTGT</td><td align="left">502</td><td align="left">User</td><td align="center">No</td></tr><tr><td align="left">Domain Admins</td><td align="left">512</td><td align="left">Group</td><td align="center">Yes</td></tr><tr><td align="left">Domain Users</td><td align="left">513</td><td align="left">Group</td><td align="center">Yes</td></tr><tr><td align="left">Domain Guests</td><td align="left">514</td><td align="left">Group</td><td align="center">Yes</td></tr><tr><td align="left">Domain Computers</td><td align="left">515</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Controllers</td><td align="left">516</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Certificate Admins</td><td align="left">517</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Schema Admins</td><td align="left">518</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Enterprise Admins</td><td align="left">519</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Domain Policy Admins</td><td align="left">520</td><td align="left">Group</td><td align="center">No</td></tr><tr><td align="left">Builtin Admins</td><td align="left">544</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin users</td><td align="left">545</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Guests</td><td align="left">546</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Power Users</td><td align="left">547</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Account Operators</td><td align="left">548</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin System Operators</td><td align="left">549</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Print Operators</td><td align="left">550</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Backup Operators</td><td align="left">551</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin Replicator</td><td align="left">552</td><td align="left">Alias</td><td align="center">No</td></tr><tr><td align="left">Builtin RAS Servers</td><td align="left">553</td><td align="left">Alias</td><td align="center">No</td></tr></tbody></table></div></div><p><br class="table-break"> 368 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598 097"></a>Example Configuration</h3></div></div></div><p>369 <a class="indexterm" name="id25981 05"></a>368 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598143"></a>Example Configuration</h3></div></div></div><p> 369 <a class="indexterm" name="id2598151"></a> 370 370 You can list the various groups in the mapping database by executing 371 371 <code class="literal">net groupmap list</code>. Here is an example: 372 372 </p><p> 373 <a class="indexterm" name="id25981 27"></a>373 <a class="indexterm" name="id2598173"></a> 374 374 </p><pre class="screen"> 375 375 <code class="prompt">root# </code> <strong class="userinput"><code>net groupmap list</code></strong> … … 380 380 </p><p> 381 381 For complete details on <code class="literal">net groupmap</code>, refer to the net(8) man page. 382 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598 174"></a>Configuration Scripts</h2></div></div></div><p>382 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598220"></a>Configuration Scripts</h2></div></div></div><p> 383 383 Everyone needs tools. Some of us like to create our own, others prefer to use canned tools 384 384 (i.e., prepared by someone else for general use). 385 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598 186"></a>Sample <code class="filename">smb.conf</code> Add Group Script</h3></div></div></div><p>386 <a class="indexterm" name="id2598 199"></a>387 <a class="indexterm" name="id25982 06"></a>388 <a class="indexterm" name="id25982 13"></a>389 <a class="indexterm" name="id25982 20"></a>390 <a class="indexterm" name="id25982 27"></a>385 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598231"></a>Sample <code class="filename">smb.conf</code> Add Group Script</h3></div></div></div><p> 386 <a class="indexterm" name="id2598245"></a> 387 <a class="indexterm" name="id2598252"></a> 388 <a class="indexterm" name="id2598259"></a> 389 <a class="indexterm" name="id2598266"></a> 390 <a class="indexterm" name="id2598273"></a> 391 391 A script to create complying group names for use by the Samba group interfaces 392 392 is provided in <a class="link" href="groupmapping.html#smbgrpadd.sh" title="Example 12.1. smbgrpadd.sh">smbgrpadd.sh</a>. This script … … 416 416 <code class="filename">smb.conf</code> for the add group Script</a> demonstrates how it may be used. 417 417 418 </p><div class="example"><a name="smbgrpadd"></a><p class="title"><b>Example 12.2. Configuration of <code class="filename">smb.conf</code> for the add group Script</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id25983 42"></a><em class="parameter"><code>add group script = /path_to_tool/smbgrpadd.sh "%g"</code></em></td></tr></table></div></div><p><br class="example-break">419 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598 357"></a>Script to Configure Group Mapping</h3></div></div></div><p>420 <a class="indexterm" name="id2598 366"></a>418 </p><div class="example"><a name="smbgrpadd"></a><p class="title"><b>Example 12.2. Configuration of <code class="filename">smb.conf</code> for the add group Script</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2598388"></a><em class="parameter"><code>add group script = /path_to_tool/smbgrpadd.sh "%g"</code></em></td></tr></table></div></div><p><br class="example-break"> 419 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598403"></a>Script to Configure Group Mapping</h3></div></div></div><p> 420 <a class="indexterm" name="id2598411"></a> 421 421 In our example we have created a UNIX/Linux group called <code class="literal">ntadmin</code>. 422 422 Our script will create the additional groups <code class="literal">Orks</code>, <code class="literal">Elves</code>, and <code class="literal">Gnomes</code>. … … 424 424 For the sake of convenience we elect to save this script as a file called <code class="filename">initGroups.sh</code>. 425 425 This script is given in <a class="link" href="groupmapping.html#set-group-map" title="Example 12.3. Script to Set Group Mapping">intGroups.sh</a>. 426 <a class="indexterm" name="id25984 16"></a>426 <a class="indexterm" name="id2598461"></a> 427 427 </p><div class="example"><a name="set-group-map"></a><p class="title"><b>Example 12.3. Script to Set Group Mapping</b></p><div class="example-contents"><pre class="programlisting"> 428 428 #!/bin/bash … … 451 451 must now be manually and explicitly created and mapped to a valid UNIX GID by the Samba 452 452 administrator. 453 </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598 485"></a>Common Errors</h2></div></div></div><p>453 </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598530"></a>Common Errors</h2></div></div></div><p> 454 454 At this time there are many little surprises for the unwary administrator. In a real sense 455 455 it is imperative that every step of automated control scripts be carefully tested 456 456 manually before putting it into active service. 457 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598 497"></a>Adding Groups Fails</h3></div></div></div><p>458 <a class="indexterm" name="id25985 05"></a>457 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598543"></a>Adding Groups Fails</h3></div></div></div><p> 458 <a class="indexterm" name="id2598551"></a> 459 459 This is a common problem when the <code class="literal">groupadd</code> is called directly 460 460 by the Samba interface script for the <a class="link" href="smb.conf.5.html#ADDGROUPSCRIPT" target="_top">add group script</a> in 461 461 the <code class="filename">smb.conf</code> file. 462 462 </p><p> 463 <a class="indexterm" name="id25985 42"></a>464 <a class="indexterm" name="id25985 49"></a>463 <a class="indexterm" name="id2598588"></a> 464 <a class="indexterm" name="id2598595"></a> 465 465 The most common cause of failure is an attempt to add an MS Windows group account 466 466 that has an uppercase character and/or a space character in it. 467 467 </p><p> 468 <a class="indexterm" name="id2598 562"></a>468 <a class="indexterm" name="id2598608"></a> 469 469 There are three possible workarounds. First, use only group names that comply 470 470 with the limitations of the UNIX/Linux <code class="literal">groupadd</code> system tool. … … 473 473 for the MS Windows group name, then use the procedure listed above to map that group 474 474 to the MS Windows group. 475 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598 584"></a>Adding Domain Users to the Workstation Power Users Group</h3></div></div></div><p>“<span class="quote">475 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2598630"></a>Adding Domain Users to the Workstation Power Users Group</h3></div></div></div><p>“<span class="quote"> 476 476 What must I do to add domain users to the Power Users group? 477 477 </span>”</p><p> 478 <a class="indexterm" name="id2598 598"></a>478 <a class="indexterm" name="id2598644"></a> 479 479 The Power Users group is a group that is local to each Windows 200x/XP Professional workstation. 480 480 You cannot add the Domain Users group to the Power Users group automatically, it must be done on
Note:
See TracChangeset
for help on using the changeset viewer.
