1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
|
<?xml version="1.0" encoding="iso8859-1"?>
<chapter id="groupmapping">
<chapterinfo>
<author>
<firstname>Jean François</firstname><surname>Micouleau</surname>
</author>
&author.jerry;
&author.jht;
</chapterinfo>
<title>Configuring Group Mapping</title>
<para>
Starting with Samba-3, new group mapping functionality is available to create associations
between Windows group SIDs and UNIX groups. The <parameter>groupmap</parameter> subcommand
included with the &net; tool can be used to manage these associations.
</para>
<warning>
<para>
The first immediate reason to use the group mapping on a Samba PDC, is that
the <parameter>domain admin group</parameter> has been removed and should no longer
be specified in &smb.conf;. This parameter was used to give the listed users membership
in the "Domain Admins" Windows group which gave local admin rights on their workstations
(in default configurations).
</para>
</warning>
<sect1>
<title>Features and Benefits</title>
<para>
Stuff goes here.
</para>
</sect1>
<sect1>
<title>Discussion</title>
<para>
When installing MS Windows NT4 / 200x on a computer, the installation program creates default
users and groups. Notably the 'Administrators' group, and gives to that group privileges necessary
privilidges to perform essential system tasks. eg: Ability to change the date and time or to
kill any process (or close too) running on the local machine.
</para>
<para>
The 'Administrator' user is a member of the 'Administrators' group, and thus inherits
'Administrators' group privileges. If a 'joe' user is created to be a member of the
'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.
</para>
<para>
When an MS Windows NT4 / W200x is made a domain member, the "Domain Adminis" group of the
PDC is added to the local 'Administrators' group of the workstation. Every member of the
'Domain Administrators' group inherits the rights of the local 'Administrators' group when
logging on the workstation.
</para>
<para>
The following steps describe how to make samba PDC users members of the 'Domain Admins' group?
</para>
<orderedlist>
<listitem><para>
create a unix group (usually in <filename>/etc/group</filename>), let's call it domadm
</para></listitem>
<listitem><para>add to this group the users that must be Administrators. For example
if you want joe,john and mary, your entry in <filename>/etc/group</filename> will
look like:
</para>
<para><screen>
domadm:x:502:joe,john,mary
</screen>
</para></listitem>
<listitem><para>
Map this domadm group to the "Domain Admins" group by running the command:
</para>
<para>
<screen>
&rootprompt;<userinput>net groupmap add ntgroup="Domain Admins" unixgroup=domadm</userinput>
</screen>
</para>
<para>
The quotes around "Domain Admins" are necessary due to the space in the group name.
Also make sure to leave no whitespace surrounding the equal character (=).
</para></listitem>
</orderedlist>
<para>
Now joe, john and mary are domain administrators!
</para>
<para>
It is possible to map any arbitrary UNIX group to any Windows NT4 / 200x group as well as
making any UNIX group a Windows domain group. For example, if you wanted to include a
UNIX group (e.g. acct) in a ACL on a local file or printer on a domain member machine,
you would flag that group as a domain group by running the following on the Samba PDC:
</para>
<para>
<screen>
&rootprompt;<userinput>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct</userinput>
</screen>
</para>
<para>
Be aware that the RID parmeter is a unsigned 32 bit integer that should
normally start at 1000. However, this rid must not overlap with any RID assigned
to a user. Verifying this is done differently depending on on the passdb backend
you are using. Future versions of the tools may perform the verification automatically,
but for now the burden is on you.
</para>
<sect2>
<title>Example Configuration</title>
<para>
You can list the various groups in the mapping database by executing
<command>net groupmap list</command>. Here is an example:
</para>
<para>
<screen>&rootprompt; net groupmap list
System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
</screen>
</para>
<para>
For complete details on <command>net groupmap</command>, refer to the net(8) man page.
</para>
</sect2>
</sect1>
<sect1>
<title>Configuration Scripts</title>
<para>
Everyone needs tools. Some of us like to create our own, others prefer to use canned tools
(ie: prepared by someone else for general use).
</para>
</sect1>
<sect1>
<title>Common Errors</title>
<para>
There must be some stuff that can go here!
</para>
</sect1>
</chapter>
|
