~zulcss/samba/server-dailies-3.4

<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�24.�Winbind: Use of Domain Accounts</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.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="VFS.html" title="Chapter�23.�Stackable VFS modules"><link rel="next" href="AdvancedNetworkManagement.html" title="Chapter�25.�Advanced Network Management"></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�24.�Winbind: Use of Domain Accounts</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="VFS.html">Prev</a>�</td><th width="60%" align="center">Part�III.�Advanced Configuration</th><td width="20%" align="right">�<a accesskey="n" href="AdvancedNetworkManagement.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="winbind"></a>Chapter�24.�Winbind: Use of Domain Accounts</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Tim</span> <span class="orgname">Samba Team</span> <span class="surname">Potter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:tpot@linuxcare.com.au">tpot@linuxcare.com.au</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Andrew</span> <span class="orgname">Samba Team</span> <span class="surname">Tridgell</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:tridge@samba.org">tridge@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Naag</span> <span class="surname">Mummaneni</span></h3><span class="contrib">Notes for Solaris</span>�<div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:getnag@rediffmail.com">getnag@rediffmail.com</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="orgname">SNAP</span> <span class="surname">Trostel</span></h3><div class="affiliation"><span class="orgname">SNAP<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jtrostel@snapserver.com">jtrostel@snapserver.com</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></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><p class="pubdate">June 15, 2005</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="winbind.html#id2653125">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653468">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2653558">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653711">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2653756">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2653882">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2653932">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654026">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654073">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654305">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654460">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654536">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2654593">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2654599">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654713">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2654865">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id2657284">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id2657333">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id2657374">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id2657411">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653125"></a>Features and Benefits</h2></div></div></div><p>

Integration of UNIX and Microsoft Windows NT through a unified logon has

been considered a “<span class="quote">holy grail</span>” in heterogeneous computing environments for

a long time.

</p><p>

There is one other facility without which UNIX and Microsoft Windows network

interoperability would suffer greatly. It is imperative that there be a

mechanism for sharing files across UNIX systems and to be able to assign

domain user and group ownerships with integrity.

</p><p>

<span class="emphasis"><em>winbind</em></span> is a component of the Samba suite of programs that

solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft

RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to

allow Windows NT domain users to appear and operate as UNIX users on a UNIX

machine. This chapter describes the Winbind system, the functionality

it provides, how it is configured, and how it works internally.

</p><p>

Winbind provides three separate functions:

</p><div class="itemizedlist"><ul type="disc"><li><p>

Authentication of user credentials (via PAM). This makes it possible to

log onto a UNIX/Linux system using user and group accounts from a Windows

NT4 (including a Samba domain) or an Active Directory domain.

</p></li><li><p>

Identity resolution (via NSS). This is the default when winbind is not used.

</p></li><li><p>

Winbind maintains a database called winbind_idmap.tdb in which it stores

mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only

for users and groups that do not have a local UID/GID. It stores the UID/GID

allocated from the idmap uid/gid range that it has mapped to the NT SID.

If <em class="parameter"><code>idmap backend</code></em> has been specified as <code class="constant">ldap:ldap://hostname[:389]</code>,

then instead of using a local mapping, Winbind will obtain this information

from the LDAP database.

</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>

If <code class="literal">winbindd</code> is not running, smbd (which calls <code class="literal">winbindd</code>) will fall back to

using purely local information from <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> and no dynamic

mapping will be used. On an operating system that has been enabled with the NSS,

the resolution of user and group information will be accomplished via NSS.

</p></div><div class="figure"><a name="winbind_idmap"></a><p class="title"><b>Figure�24.1.�Winbind Idmap</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap_winbind_no_loop.png" width="243" alt="Winbind Idmap"></div></div></div><br class="figure-break"></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653468"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have

different models for representing user and group information and

use different technologies for implementing them. This fact has

made it difficult to integrate the two systems in a satisfactory

manner.</p><p>

One common solution in use today has been to create

identically named user accounts on both the UNIX and Windows systems

and use the Samba suite of programs to provide file and print services

between the two. This solution is far from perfect, however, because

adding and deleting users on both sets of machines becomes a chore,

and two sets of passwords are required both of which

can lead to synchronization problems between the UNIX and Windows

systems and confusion for users.</p><p>We divide the unified logon problem for UNIX machines into

three smaller problems:</p><div class="itemizedlist"><ul type="disc"><li><p>Obtaining Windows NT user and group information.

</p></li><li><p>Authenticating Windows NT users.

</p></li><li><p>Password changing for Windows NT users.

</p></li></ul></div><p>

Ideally, a prospective solution to the unified logon problem

would satisfy all the above components without duplication of

information on the UNIX machines and without creating additional

tasks for the system administrator when maintaining users and

groups on either system. The Winbind system provides a simple

and elegant solution to all three components of the unified logon

problem.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653558"></a>What Winbind Provides</h2></div></div></div><p>

Winbind unifies UNIX and Windows NT account management by

allowing a UNIX box to become a full member of an NT domain. Once

this is done, the UNIX box will see NT users and groups as if

100

they were “<span class="quote">native</span>” UNIX users and groups, allowing the NT domain

101

to be used in much the same manner that NIS+ is used within

102

UNIX-only environments.</p><p>

103

104

105

106

107

The end result is that whenever a

108

program on the UNIX machine asks the operating system to look up

109

a user or group name, the query will be resolved by asking the

110

NT domain controller for the specified domain to do the lookup.

111

Because Winbind hooks into the operating system at a low level

112

(via the NSS name resolution modules in the C library), this

113

redirection to the NT domain controller is completely

114

transparent.</p><p>

115

116

117

Users on the UNIX machine can then use NT user and group

118

names as they would “<span class="quote">native</span>” UNIX names. They can chown files

119

so they are owned by NT domain users or even login to the

120

UNIX machine and run a UNIX X-Window session as a domain user.</p><p>

121

122

The only obvious indication that Winbind is being used is

123

that user and group names take the form <code class="constant">DOMAIN\user</code> and

124

<code class="constant">DOMAIN\group</code>. This is necessary because it allows Winbind to determine

125

that redirection to a domain controller is wanted for a particular

126

lookup and which trusted domain is being referenced.</p><p>

127

128

129

Additionally, Winbind provides an authentication service that hooks into the PAM system

130

to provide authentication via an NT domain to any PAM-enabled

131

applications. This capability solves the problem of synchronizing

132

passwords between systems, since all passwords are stored in a single

133

location (on the domain controller).</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653711"></a>Target Uses</h3></div></div></div><p>

134

135

Winbind is targeted at organizations that have an

136

existing NT-based domain infrastructure into which they wish

137

to put UNIX workstations or servers. Winbind will allow these

138

organizations to deploy UNIX workstations without having to

139

maintain a separate account infrastructure. This greatly

140

simplifies the administrative overhead of deploying UNIX

141

workstations into an NT-based organization.</p><p>

142

143

144

Another interesting way in which we expect Winbind to

145

be used is as a central part of UNIX-based appliances. Appliances

146

that provide file and print services to Microsoft-based networks

147

will be able to use Winbind to provide seamless integration of

148

the appliance into the domain.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653756"></a>Handling of Foreign SIDs</h3></div></div></div><p>

149

150

The term <span class="emphasis"><em>foreign SID</em></span> is often met with the reaction that it

151

is not relevant to a particular environment. The following documents an interchange

152

that took place on the Samba mailing list. It is a good example of the confusion

153

often expressed regarding the use of winbind.

154

</p><p>

155

156

Fact: Winbind is needed to handle users who use workstations that are NOT part

157

of the local domain.

158

</p><p>

159

160

Response: “<span class="quote">Why? I've used Samba with workstations that are not part of my domains

161

lots of times without using winbind. I thought winbind was for using Samba as a member server

162

in a domain controlled by another Samba/Windows PDC.</span>”

163

</p><p>

164

165

166

167

If the Samba server will be accessed from a domain other than the local Samba domain, or

168

if there will be access from machines that are not local domain members, winbind will

169

permit the allocation of UIDs and GIDs from the assigned pool that will keep the identity

170

of the foreign user separate from users that are members of the Samba domain.

171

</p><p>

172

173

174

175

176

This means that winbind is eminently useful in cases where a single

177

Samba PDC on a local network is combined with both domain member and domain non-member workstations.

178

If winbind is not used, the user george on a Windows workstation that is not a domain

179

member will be able to access the files of a user called george in the account database

180

of the Samba server that is acting as a PDC. When winbind is used, the default condition

181

is that the local user george will be treated as the account DOMAIN\george and the

182

foreign (non-member of the domain) account will be treated as MACHINE\george because

183

each has a different SID.

184

</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2653882"></a>How Winbind Works</h2></div></div></div><p>

185

186

187

188

189

The Winbind system is designed around a client/server

190

architecture. A long-running <code class="literal">winbindd</code> daemon

191

listens on a UNIX domain socket waiting for requests

192

to arrive. These requests are generated by the NSS and PAM

193

clients and are processed sequentially.</p><p>The technologies used to implement Winbind are described

194

in detail below.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2653932"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p>

195

196

197

198

199

200

Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of

201

the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations

202

between Windows NT machines, including remote management, user authentication, and print spooling. Although

203

initially this work was done to aid the implementation of Primary Domain Controller (PDC) functionality in

204

Samba, it has also yielded a body of code that can be used for other purposes.

205

</p><p>

206

207

208

209

Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about

210

individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user

211

passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account

212

information onto UNIX user and group names.

213

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654026"></a>Microsoft Active Directory Services</h3></div></div></div><p>

214

215

216

217

218

Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its “<span class="quote">native

219

mode</span>” protocols rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running

220

Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing

221

provide a much more efficient and effective Winbind implementation.

222

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654073"></a>Name Service Switch</h3></div></div></div><p>

223

224

225

226

227

The NSS is a feature that is present in many UNIX operating systems. It allows system

228

information such as hostnames, mail aliases, and user information

229

to be resolved from different sources. For example, a standalone

230

UNIX workstation may resolve system information from a series of

231

flat files stored on the local file system. A networked workstation

232

may first attempt to resolve system information from local files,

233

and then consult an NIS database for user information or a DNS server

234

for hostname information.</p><p>

235

236

237

238

239

240

The NSS application programming interface allows Winbind to present itself as a source of system

241

information when resolving UNIX usernames and groups. Winbind uses this interface and information obtained

242

from a Windows NT server using MSRPC calls to provide a new source of account enumeration. Using standard UNIX

243

library calls, you can enumerate the users and groups on a UNIX machine running Winbind and see all users and

244

groups in an NT domain plus any trusted domain as though they were local users and groups.

245

</p><p>

246

247

248

249

The primary control file for NSS is <code class="filename">/etc/nsswitch.conf</code>. When a UNIX application

250

makes a request to do a lookup, the C library looks in <code class="filename">/etc/nsswitch.conf</code> for a line that

251

matches the service type being requested; for example, the “<span class="quote">passwd</span>” service type is used when

252

user or group names are looked up. This config line specifies which implementations of that service should be

253

tried and in what order. If the passwd config line is:

254

</p><pre class="screen">

255

passwd: files example

256

</pre><p>

257

258

259

260

then the C library will first load a module called <code class="filename">/lib/libnss_files.so</code> followed

261

by the module <code class="filename">/lib/libnss_example.so</code>. The C library will dynamically load each of these

262

modules in turn and call resolver functions within the modules to try to resolve the request. Once the request

263

is resolved, the C library returns the result to the application.

264

</p><p>

265

266

267

268

This NSS interface provides an easy way for Winbind to hook into the operating system. All that needs

269

to be done is to put <code class="filename">libnss_winbind.so</code> in <code class="filename">/lib/</code> then add

270

“<span class="quote">winbind</span>” into <code class="filename">/etc/nsswitch.conf</code> at the appropriate place. The C library

271

will then call Winbind to resolve user and group names.

272

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654305"></a>Pluggable Authentication Modules</h3></div></div></div><p>

273

274

275

276

277

PAMs provide a system for abstracting authentication and authorization technologies. With a PAM

278

module, it is possible to specify different authentication methods for different system applications without

279

having to recompile these applications. PAM is also useful for implementing a particular policy for

280

authorization. For example, a system administrator may only allow console logins from users stored in the

281

local password file but only allow users resolved from an NIS database to log in over the network.

282

</p><p>

283

284

285

286

287

288

Winbind uses the authentication management and password management PAM interface to integrate Windows

289

NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated

290

against a suitable PDC. These users can also change their passwords and have this change take effect directly

291

on the PDC.

292

</p><p>

293

294

295

296

297

PAM is configured by providing control files in the directory <code class="filename">/etc/pam.d/</code> for

298

each of the services that require authentication. When an authentication request is made by an application,

299

the PAM code in the C library looks up this control file to determine what modules to load to do the

300

authentication check and in what order. This interface makes adding a new authentication service for Winbind

301

very easy: simply copy the <code class="filename">pam_winbind.so</code> module to <code class="filename">/lib/security/</code>,

302

and the PAM control files for relevant services are updated to allow authentication via Winbind. See the PAM

303

documentation in <a class="link" href="pam.html" title="Chapter�28.�PAM-Based Distributed Authentication">PAM-Based Distributed Authentication</a>, for more information.

304

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654460"></a>User and Group ID Allocation</h3></div></div></div><p>

305

306

307

308

When a user or group is created under Windows NT/200x, it is allocated a numerical relative identifier

309

(RID). This is slightly different from UNIX, which has a range of numbers that are used to identify users and

310

the same range used to identify groups. It is Winbind's job to convert RIDs to UNIX ID numbers and vice versa.

311

When Winbind is configured, it is given part of the UNIX user ID space and a part of the UNIX group ID space

312

in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is

313

allocated the next UNIX ID from the range. The same process applies for Windows NT groups. Over time, Winbind

314

will have mapped all Windows NT users and groups to UNIX user IDs and group IDs.

315

</p><p>

316

317

318

319

320

The results of this mapping are stored persistently in an ID mapping database held in a tdb database.

321

This ensures that RIDs are mapped to UNIX IDs in a consistent way.

322

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654536"></a>Result Caching</h3></div></div></div><p>

323

324

325

326

327

328

An active directory system can generate a lot of user and group name lookups. To reduce the network

329

cost of these lookups, Winbind uses a caching scheme based on the SAM sequence number supplied by NT domain

330

controllers. User or group information returned by a PDC is cached by Winbind along with a sequence number

331

also returned by the PDC. This sequence number is incremented by Windows NT whenever any user or group

332

information is modified. If a cached entry has expired, the sequence number is requested from the PDC and

333

compared against the sequence number of the cached entry. If the sequence numbers do not match, then the

334

cached information is discarded and up-to-date information is requested directly from the PDC.

335

</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2654593"></a>Installation and Configuration</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654599"></a>Introduction</h3></div></div></div><p>

336

337

338

339

This section describes the procedures used to get Winbind up and running. Winbind is capable of providing

340

access and authentication control for Windows Domain users through an NT or Windows 200x PDC for regular

341

services, such as telnet and ftp, as well for Samba services.

342

</p><div class="itemizedlist"><ul type="disc"><li><p>

343

<span class="emphasis"><em>Why should I do this?</em></span>

344

</p><p>

345

346

347

348

349

This allows the Samba administrator to rely on the authentication mechanisms on the Windows NT/200x PDC

350

for the authentication of domain members. Windows NT/200x users no longer need to have separate accounts on

351

the Samba server.

352

</p></li><li><p>

353

<span class="emphasis"><em>Who should be reading this document?</em></span>

354

</p><p>

355

356

357

This document is designed for system administrators. If you are implementing Samba on a file server and wish

358

to (fairly easily) integrate existing Windows NT/200x users from your PDC onto the Samba server, this document

359

is for you.

360

</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654713"></a>Requirements</h3></div></div></div><p>

361

362

363

364

If you have a Samba configuration file that you are currently using, <span class="emphasis"><em>BACK IT UP!</em></span>

365

If your system already uses PAM, <span class="emphasis"><em>back up the <code class="filename">/etc/pam.d</code> directory

366

contents!</em></span> If you haven't already made a boot disk, <span class="emphasis"><em>MAKE ONE NOW!</em></span>

367

</p><p>

368

369

370

371

Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's

372

why you want to be able to boot back into your machine in single-user mode and restore your

373

<code class="filename">/etc/pam.d</code> to the original state it was in if you get frustrated with the

374

way things are going.

375

</p><p>

376

377

378

The latest version of Samba-3 includes a functioning winbindd daemon. Please refer to the <a class="ulink" href="http://samba.org/" target="_top">main Samba Web page</a>, or better yet, your closest Samba mirror site for

379

instructions on downloading the source code.

380

</p><p>

381

382

383

384

385

To allow domain users the ability to access Samba shares and files, as well as potentially other services

386

provided by your Samba machine, PAM must be set up properly on your

387

machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed

388

on your system. Please refer to the PAM Web site <a class="ulink" href="http://www.kernel.org/pub/linux/libs/pam/" target="_top">http://www.kernel.org/pub/linux/libs/pam/</a>.

389

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2654865"></a>Testing Things Out</h3></div></div></div><p>

390

391

392

393

394

395

Before starting, it is probably best to kill off all the Samba-related daemons running on your server.

396

Kill off all <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> processes that may be running. To use PAM,

397

make sure that you have the standard PAM package that supplies the <code class="filename">/etc/pam.d</code>

398

directory structure, including the PAM modules that are used by PAM-aware services, several PAM libraries,

399

and the <code class="filename">/usr/doc</code> and <code class="filename">/usr/man</code> entries for PAM. Winbind is built

400

better in Samba if the pam-devel package is also installed. This package includes the header files

401

needed to compile PAM-aware applications.

402

</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2654952"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p>

403

404

405

406

407

PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install

408

the <code class="filename">pam-devel</code> libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3

409

may auto-install the Winbind files into their correct locations on your system, so before you get too far down

410

the track, be sure to check if the following configuration is really

411

necessary. You may only need to configure

412

<code class="filename">/etc/nsswitch.conf</code>.

413

</p><p>

414

The libraries needed to run the <span class="application">winbindd</span> daemon through nsswitch need to be copied to their proper locations:

415

</p><p>

416

417

</p><pre class="screen">

418

<code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/libnss_winbind.so /lib</code></strong>

419

</pre><p>

420

</p><p>

421

I also found it necessary to make the following symbolic link:

422

</p><p>

423

<code class="prompt">root# </code> <strong class="userinput"><code>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</code></strong>

424

</p><p>And, in the case of Sun Solaris:

425

426

</p><pre class="screen">

427

<code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</code></strong>

428

<code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.1</code></strong>

429

<code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/nss_winbind.so.2</code></strong>

430

</pre><p>

431

</p><p>

432

433

As root, edit <code class="filename">/etc/nsswitch.conf</code> to allow user and group entries to be visible from the

434

<span class="application">winbindd</span> daemon. My <code class="filename">/etc/nsswitch.conf</code> file looked like this after editing:

435

</p><pre class="programlisting">

436

passwd: files winbind

437

shadow: files

438

group: files winbind

439

</pre><p>

440

441

442

443

444

445

The libraries needed by the <code class="literal">winbindd</code> daemon will be automatically

446

entered into the <code class="literal">ldconfig</code> cache the next time

447

your system reboots, but it is faster (and you do not need to reboot) if you do it manually:

448

</p><pre class="screen">

449

<code class="prompt">root# </code><strong class="userinput"><code>/sbin/ldconfig -v | grep winbind</code></strong>

450

</pre><p>

451

This makes <code class="filename">libnss_winbind</code> available to winbindd and reports the current

452

search path that is used by the dynamic link loader. The use of the <code class="literal">grep</code>

453

filters the output of the <code class="literal">ldconfig</code> command so that we may see proof that

454

this library is indeed recognized by the dynamic link loader.

455

</p><p>

456

457

458

459

460

461

The Sun Solaris dynamic link loader management tool is called <code class="literal">crle</code>. The

462

use of this tool is necessary to instruct the dynamic link loader to search directories that

463

contain library files that were not supplied as part of the original operating system platform.

464

The following example shows how to use this tool to add the directory <code class="filename">/usr/local/lib</code>

465

to the dynamic link loader's search path:

466

</p><pre class="screen">

467

<code class="prompt">root# </code> crle -u -l /usr/lib:/usr/local/lib

468

</pre><p>

469

When executed without arguments, <code class="literal">crle</code> reports the current dynamic

470

link loader configuration. This is demonstrated here:

471

</p><pre class="screen">

472

<code class="prompt">root# </code> crle

473

474

Configuration file [version 4]: /var/ld/ld.config

475

Default Library Path (ELF): /lib:/usr/lib:/usr/local/lib

476

Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system default)

477

478

Command line:

479

crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/local/lib

480

</pre><p>

481

From this it is apparent that the <code class="filename">/usr/local/lib</code> directory is included

482

in the search dynamic link libraries in order to satisfy object module dependencies.

483

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655350"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p>

484

485

486

487

488

489

490

The Winbind AIX identification module gets built as <code class="filename">libnss_winbind.so</code> in the

491

nsswitch directory of the Samba source. This file can be copied to <code class="filename">/usr/lib/security</code>,

492

and the AIX naming convention would indicate that it should be named WINBIND. A stanza like the following:

493

</p><pre class="programlisting">

494

WINBIND:

495

program = /usr/lib/security/WINBIND

496

options = authonly

497

</pre><p>

498

can then be added to <code class="filename">/usr/lib/security/methods.cfg</code>. This module only supports

499

identification, but there have been reports of success using the standard Winbind PAM module for

500

authentication. Use caution configuring loadable authentication modules, since misconfiguration can make

501

it impossible to log on to the system. Information regarding the AIX authentication module API can

502

be found in the “<span class="quote">Kernel Extensions and Device Support Programming Concepts for AIX</span>” document that

503

describes the <a class="ulink" href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/kernextc/sec_load_mod.htm" target="_top">

504

Loadable Authentication Module Programming Interface</a> for AIX. Further information on administering the modules

505

can be found in the <a class="ulink" href="http://publibn.boulder.ibm.com/doc_link/en_US/a_doc_lib/aixbman/baseadmn/iandaadmin.htm" target="_top">System

506

Management Guide: Operating System and Devices.</a>

507

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655464"></a>Configure smb.conf</h4></div></div></div><p>

508

509

510

511

Several parameters are needed in the <code class="filename">smb.conf</code> file to control the behavior of <span class="application">winbindd</span>. These

512

are described in more detail in the <a class="citerefentry" href="winbindd.8.html"><span class="citerefentry"><span class="refentrytitle">winbindd</span>(8)</span></a> man page. My <code class="filename">smb.conf</code> file, as shown in <a class="link" href="winbind.html#winbindcfg" title="Example�24.1.�smb.conf for Winbind Setup">the smb.conf for Winbind Setup</a>, was modified to include the necessary entries in the [global] section.

513

</p><div class="example"><a name="winbindcfg"></a><p class="title"><b>Example�24.1.�smb.conf for Winbind Setup</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># separate domain and username with '\', like DOMAIN\username</td></tr><tr><td><a class="indexterm" name="id2655559"></a><em class="parameter"><code>winbind separator = \</code></em></td></tr><tr><td># use uids from 10000 to 20000 for domain users</td></tr><tr><td><a class="indexterm" name="id2655575"></a><em class="parameter"><code>idmap uid = 10000-20000</code></em></td></tr><tr><td># use gids from 10000 to 20000 for domain groups</td></tr><tr><td><a class="indexterm" name="id2655591"></a><em class="parameter"><code>idmap gid = 10000-20000</code></em></td></tr><tr><td># allow enumeration of winbind users and groups</td></tr><tr><td><a class="indexterm" name="id2655606"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2655618"></a><em class="parameter"><code>winbind enum groups = yes</code></em></td></tr><tr><td># give winbind users a real shell (only needed if they have telnet access)</td></tr><tr><td><a class="indexterm" name="id2655635"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id2655647"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655661"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p>

514

515

516

517

All machines that will participate in domain security should be members of

518

the domain. This applies also to the PDC and all BDCs.

519

</p><p>

520

521

522

523

524

525

526

527

528

529

The process of joining a domain requires the use of the <code class="literal">net rpc join</code>

530

command. This process communicates with the domain controller it will register with

531

(usually the PDC) via MS DCE RPC. This means, of course, that the <code class="literal">smbd</code>

532

process must be running on the target domain controller. It is therefore necessary to temporarily

533

start Samba on a PDC so that it can join its own domain.

534

</p><p>

535

536

537

538

Enter the following command to make the Samba server join the domain, where <em class="replaceable"><code>PDC</code></em> is

539

the name of your PDC and <em class="replaceable"><code>Administrator</code></em> is a domain user who has administrative

540

privileges in the domain.

541

</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>

542

543

544

545

546

Before attempting to join a machine to the domain, verify that Samba is running

547

on the target domain controller (usually PDC) and that it is capable of being reached via ports

548

137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx).

549

</p></div><p>

550

551

The use of the <code class="literal">net rpc join</code> facility is shown here:

552

</p><pre class="screen">

553

<code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</code></strong>

554

</pre><p>

555

The proper response to the command should be “<span class="quote">Joined the domain

556

<em class="replaceable"><code>DOMAIN</code></em></span>” where <em class="replaceable"><code>DOMAIN</code></em>

557

is your domain name.

558

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2655899"></a>Starting and Testing the <code class="literal">winbindd</code> Daemon</h4></div></div></div><p>

559

560

561

562

Eventually, you will want to modify your Samba startup script to automatically invoke the winbindd daemon when

563

the other parts of Samba start, but it is possible to test out just the Winbind portion first. To start up

564

Winbind services, enter the following command as root:

565

</p><pre class="screen">

566

<code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/sbin/winbindd</code></strong>

567

</pre><p>

568

Use the appropriate path to the location of the <code class="literal">winbindd</code> executable file.

569

</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>

570

571

572

The command to start up Winbind services assumes that Samba has been installed in the

573

<code class="filename">/usr/local/samba</code> directory tree. You may need to search for the location of Samba files

574

if this is not the location of <code class="literal">winbindd</code> on your system.

575

</p></div><p>

576

577

578

I'm always paranoid and like to make sure the daemon is really running.

579

</p><pre class="screen">

580

<code class="prompt">root# </code><strong class="userinput"><code>ps -ae | grep winbindd</code></strong>

581

</pre><p>

582

</p><p>

583

584

This command should produce output like the following if the daemon is running.

585

</p><pre class="screen">

586

3025 ? 00:00:00 winbindd

587

</pre><p>

588

</p><p>

589

590

591

Now, for the real test, try to get some information about the users on your PDC:

592

</p><pre class="screen">

593

<code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/wbinfo -u</code></strong>

594

</pre><p>

595

This should echo back a list of users on your Windows users on your PDC. For example, I get the following

596

response:

597

</p><pre class="screen">

598

CEO\Administrator

599

CEO\burdell

600

CEO\Guest

601

CEO\jt-ad

602

CEO\krbtgt

603

CEO\TsInternetUser

604

</pre><p>

605

Obviously, I have named my domain “<span class="quote">CEO</span>” and my <a class="link" href="smb.conf.5.html#WINBINDSEPARATOR" target="_top">winbind separator</a> is

606

“<span class="quote">\</span>”.

607

</p><p>

608

609

610

You can do the same sort of thing to get group information from the PDC:

611

</p><pre class="screen">

612

<code class="prompt">root# </code><strong class="userinput"><code>/usr/local/samba/bin/wbinfo -g</code></strong>

613

CEO\Domain Admins

614

CEO\Domain Users

615

CEO\Domain Guests

616

CEO\Domain Computers

617

CEO\Domain Controllers

618

CEO\Cert Publishers

619

CEO\Schema Admins

620

CEO\Enterprise Admins

621

CEO\Group Policy Creator Owners

622

</pre><p>

623

624

625

626

627

628

629

630

The function <code class="literal">getent</code> can now be used to get unified lists of both local and PDC users and

631

groups. Try the following command:

632

</p><pre class="screen">

633

<code class="prompt">root# </code><strong class="userinput"><code>getent passwd</code></strong>

634

</pre><p>

635

You should get a list that looks like your <code class="filename">/etc/passwd</code>

636

list followed by the domain users with their new UIDs, GIDs, home

637

directories, and default shells.

638

</p><p>

639

The same thing can be done for groups with the command:

640

</p><pre class="screen">

641

<code class="prompt">root# </code><strong class="userinput"><code>getent group</code></strong>

642

</pre><p>

643

</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2656253"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656259"></a>Linux</h5></div></div></div><p>

644

645

646

647

648

649

650

651

652

653

The <span class="application">winbindd</span> daemon needs to start up after the <span class="application">smbd</span> and <span class="application">nmbd</span> daemons are running. To accomplish this

654

task, you need to modify the startup scripts of your system. They are located at

655

<code class="filename">/etc/init.d/smb</code> in Red Hat Linux and in <code class="filename">/etc/init.d/samba</code> in Debian

656

Linux. Edit your script to add commands to invoke this daemon in the proper sequence. My startup script starts

657

up <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> from the <code class="filename">/usr/local/samba/bin</code> directory directly. The

658

<code class="literal">start</code> function in the script looks like this:

659

</p><pre class="programlisting">

660

start() {

661

KIND="SMB"

662

echo -n $"Starting $KIND services: "

663

daemon /usr/local/samba/bin/smbd $SMBDOPTIONS

664

RETVAL=$?

665

echo

666

KIND="NMB"

667

echo -n $"Starting $KIND services: "

668

daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS

669

RETVAL2=$?

670

echo

671

KIND="Winbind"

672

echo -n $"Starting $KIND services: "

673

daemon /usr/local/samba/sbin/winbindd

674

RETVAL3=$?

675

echo

676

[ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \

677

touch /var/lock/subsys/smb || RETVAL=1

678

return $RETVAL

679

}

680

</pre><p>If you would like to run winbindd in dual daemon mode, replace the line:

681

</p><pre class="programlisting">

682

daemon /usr/local/samba/sbin/winbindd

683

</pre><p>

684

685

in the example above with:

686

687

</p><pre class="programlisting">

688

daemon /usr/local/samba/sbin/winbindd -D

689

</pre><p>.

690

</p><p>

691

The <code class="literal">stop</code> function has a corresponding entry to shut down the services and looks like this:

692

</p><pre class="programlisting">

693

stop() {

694

KIND="SMB"

695

echo -n $"Shutting down $KIND services: "

696

killproc smbd

697

RETVAL=$?

698

echo

699

KIND="NMB"

700

echo -n $"Shutting down $KIND services: "

701

killproc nmbd

702

RETVAL2=$?

703

echo

704

KIND="Winbind"

705

echo -n $"Shutting down $KIND services: "

706

killproc winbindd

707

RETVAL3=$?

708

[ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && \

709

rm -f /var/lock/subsys/smb

710

echo ""

711

return $RETVAL

712

}

713

</pre></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656465"></a>Solaris</h5></div></div></div><p>

714

Winbind does not work on Solaris 9; see <a class="link" href="Portability.html#winbind-solaris9" title="Winbind on Solaris 9">Winbind on Solaris 9 section</a>

715

for details.

716

</p><p>

717

718

719

720

721

722

723

On Solaris, you need to modify the <code class="filename">/etc/init.d/samba.server</code> startup script. It

724

usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in

725

<code class="filename">/usr/local/samba/bin</code>, the file could contains something like this:

726

</p><p>

727

</p><pre class="programlisting">

728

729

## samba.server

730

731

732

if [ ! -d /usr/bin ]

733

then # /usr not mounted

734

exit

735

736

737

killproc() { # kill the named process(es)

738

pid=`/usr/bin/ps -e |

739

/usr/bin/grep -w $1 |

740

/usr/bin/sed -e 's/^ *//' -e 's/ .*//'`

741

[ "$pid" != "" ] && kill $pid

742

}

743

744

# Start/stop processes required for Samba server

745

746

case "$1" in

747

748

'start')

749

750

# Edit these lines to suit your installation (paths, workgroup, host)

751

752

echo Starting SMBD

753

/usr/local/samba/bin/smbd -D -s \

754

/usr/local/samba/smb.conf

755

756

echo Starting NMBD

757

/usr/local/samba/bin/nmbd -D -l \

758

/usr/local/samba/var/log -s /usr/local/samba/smb.conf

759

760

echo Starting Winbind Daemon

761

/usr/local/samba/sbin/winbindd

762

;;

763

764

'stop')

765

killproc nmbd

766

killproc smbd

767

killproc winbindd

768

;;

769

770

771

echo "Usage: /etc/init.d/samba.server { start | stop }"

772

;;

773

esac

774

</pre><p>

775

Again, if you would like to run Samba in dual daemon mode, replace:

776

</p><pre class="programlisting">

777

/usr/local/samba/sbin/winbindd

778

</pre><p>

779

in the script above with:

780

</p><pre class="programlisting">

781

/usr/local/samba/sbin/winbindd -D

782

</pre><p>

783

</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656610"></a>Restarting</h5></div></div></div><p>

784

785

786

If you restart the <span class="application">smbd</span>, <span class="application">nmbd</span>, and <span class="application">winbindd</span> daemons at this point, you

787

should be able to connect to the Samba server as a domain member just as

788

if you were a local user.

789

</p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2656654"></a>Configure Winbind and PAM</h4></div></div></div><p>

790

791

792

793

794

If you have made it this far, you know that <code class="literal">winbindd</code> and Samba are working together. If you

795

want to use Winbind to provide authentication for other services, keep reading. The PAM configuration files

796

need to be altered in this step. (Did you remember to make backups of your original

797

<code class="filename">/etc/pam.d</code> files? If not, do it now.)

798

</p><p>

799

800

801

802

803

804

805

You will need a PAM module to use winbindd with these other services. This module will be compiled in the

806

<code class="filename">../source/nsswitch</code> directory by invoking the command:

807

</p><pre class="screen">

808

<code class="prompt">root# </code><strong class="userinput"><code>make nsswitch/pam_winbind.so</code></strong>

809

</pre><p>

810

from the <code class="filename">../source</code> directory. The <code class="filename">pam_winbind.so</code> file should be

811

copied to the location of your other PAM security modules. On my Red Hat system, this was the

812

<code class="filename">/lib/security</code> directory. On Solaris, the PAM security modules reside in

813

<code class="filename">/usr/lib/security</code>.

814

</p><pre class="screen">

815

<code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</code></strong>

816

</pre><p>

817

</p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2656821"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p>

818

819

The <code class="filename">/etc/pam.d/samba</code> file does not need to be changed. I just left this file as it was:

820

</p><pre class="programlisting">

821

auth required /lib/security/pam_stack.so service=system-auth

822

account required /lib/security/pam_stack.so service=system-auth

823

</pre><p>

824

825

826

827

828

829

830

831

832

833

The other services that I modified to allow the use of Winbind as an authentication service were the normal

834

835

services, you may first need to change the entries in <code class="filename">/etc/xinetd.d</code> (or

836

<code class="filename">/etc/inetd.conf</code>). Red Hat Linux 7.1 and later uses the new xinetd.d structure, in this

837

case you need to change the lines in <code class="filename">/etc/xinetd.d/telnet</code> and

838

<code class="filename">/etc/xinetd.d/wu-ftp</code> from:

839

</p><pre class="programlisting">

840

enable = no

841

</pre><p>

842

843

</p><pre class="programlisting">

844

enable = yes

845

</pre><p>

846

847

848

849

For ftp services to work properly, you will also need to either have individual directories for the domain

850

users already present on the server or change the home directory template to a general directory for all

851

domain users. These can be easily set using the <code class="filename">smb.conf</code> global entry <a class="link" href="smb.conf.5.html#TEMPLATEHOMEDIR" target="_top">template homedir</a>.

852

</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>

853

854

The directory in <a class="link" href="smb.conf.5.html#TEMPLATEHOMEDIR" target="_top">template homedir</a> is not created automatically! Use pam_mkhomedir or

855

pre-create the directories of users to make sure users can log in on UNIX with their own home directory.

856

</p></div><p>

857

858

859

860

The <code class="filename">/etc/pam.d/ftp</code> file can be changed to allow Winbind ftp access in a manner similar to

861

the samba file. My <code class="filename">/etc/pam.d/ftp</code> file was changed to look like this:

862

</p><pre class="programlisting">

863

auth required /lib/security/pam_listfile.so item=user sense=deny \

864

file=/etc/ftpusers onerr=succeed

865

auth sufficient /lib/security/pam_winbind.so

866

auth required /lib/security/pam_stack.so service=system-auth

867

auth required /lib/security/pam_shells.so

868

account sufficient /lib/security/pam_winbind.so

869

account required /lib/security/pam_stack.so service=system-auth

870

session required /lib/security/pam_stack.so service=system-auth

871

</pre><p>

872

873

The <code class="filename">/etc/pam.d/login</code> file can be changed in nearly the same way. It now looks like this:

874

</p><pre class="programlisting">

875

auth required /lib/security/pam_securetty.so

876

auth sufficient /lib/security/pam_winbind.so

877

auth sufficient /lib/security/pam_unix.so use_first_pass

878

auth required /lib/security/pam_stack.so service=system-auth

879

auth required /lib/security/pam_nologin.so

880

account sufficient /lib/security/pam_winbind.so

881

account required /lib/security/pam_stack.so service=system-auth

882

password required /lib/security/pam_stack.so service=system-auth

883

session required /lib/security/pam_stack.so service=system-auth

884

session optional /lib/security/pam_console.so

885

</pre><p>

886

887

888

889

In this case, I added the </p><pre class="programlisting">auth sufficient /lib/security/pam_winbind.so</pre><p> lines

890

as before, but also added the </p><pre class="programlisting">required pam_securetty.so</pre><p> above it to disallow

891

root logins over the network. I also added a </p><pre class="programlisting">sufficient /lib/security/pam_unix.so

892

use_first_pass</pre><p> line after the <code class="literal">winbind.so</code> line to get rid of annoying

893

double prompts for passwords.

894

</p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2657167"></a>Solaris-Specific Configuration</h5></div></div></div><p>

895

896

897

The <code class="filename">/etc/pam.conf</code> needs to be changed. I changed this file so my Domain

898

users can log on both locally as well as with telnet. The following are the changes

899

that I made. You can customize the <code class="filename">pam.conf</code> file as per your requirements, but

900

be sure of those changes because in the worst case it will leave your system

901

nearly impossible to boot.

902

</p><pre class="programlisting">

903

904

#ident "@(#)pam.conf 1.14 99/09/16 SMI"

905

906

907

908

909

# PAM configuration

910

911

# Authentication management

912

913

914

915

916

917

rlogin auth sufficient /usr/lib/security/pam_winbind.so

918

rlogin auth sufficient /usr/lib/security/$ISA/pam_rhosts_auth.so.1

919

rlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass

920

921

dtlogin auth sufficient /usr/lib/security/pam_winbind.so

922

dtlogin auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass

923

924

rsh auth required /usr/lib/security/$ISA/pam_rhosts_auth.so.1

925

other auth sufficient /usr/lib/security/pam_winbind.so

926

other auth required /usr/lib/security/$ISA/pam_unix.so.1 try_first_pass

927

928

# Account management

929

930

931

932

933

934

dtlogin account sufficient /usr/lib/security/pam_winbind.so

935

dtlogin account requisite /usr/lib/security/$ISA/pam_roles.so.1

936

dtlogin account required /usr/lib/security/$ISA/pam_unix.so.1

937

938

other account sufficient /usr/lib/security/pam_winbind.so

939

other account requisite /usr/lib/security/$ISA/pam_roles.so.1

940

other account required /usr/lib/security/$ISA/pam_unix.so.1

941

942

# Session management

943

944

other session required /usr/lib/security/$ISA/pam_unix.so.1

945

946

# Password management

947

948

#other password sufficient /usr/lib/security/pam_winbind.so

949

other password required /usr/lib/security/$ISA/pam_unix.so.1

950

dtsession auth required /usr/lib/security/$ISA/pam_unix.so.1

951

952

# Support for Kerberos V5 authentication (uncomment to use Kerberos)

953

954

#rlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

955

#login auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

956

#dtlogin auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

957

#other auth optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

958

#dtlogin account optional /usr/lib/security/$ISA/pam_krb5.so.1

959

#other account optional /usr/lib/security/$ISA/pam_krb5.so.1

960

#other session optional /usr/lib/security/$ISA/pam_krb5.so.1

961

#other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass

962

</pre><p>

963

964

I also added a <em class="parameter"><code>try_first_pass</code></em> line after the <code class="filename">winbind.so</code>

965

line to get rid of annoying double prompts for passwords.

966

</p><p>

967

Now restart your Samba and try connecting through your application that you

968

configured in the pam.conf.

969

</p></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657284"></a>Conclusion</h2></div></div></div><p>

970

971

972

973

974

975

The Winbind system, through the use of the NSS, PAMs, and appropriate Microsoft RPC calls, have allowed us to

976

provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great

977

reduction in the administrative cost of running a mixed UNIX and NT network.

978

</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2657333"></a>Common Errors</h2></div></div></div><p>

979

Winbind has a number of limitations in its current released version that we hope to overcome in future releases:

980

</p><div class="itemizedlist"><ul type="disc"><li><p>

981

Winbind is currently only available for the Linux, Solaris, AIX, and IRIX operating systems, although

982

ports to other operating systems are certainly possible. For such ports to be feasible, we require the C

983

library of the target operating system to support the NSS and PAM systems. This is becoming more common as NSS

984

and PAM gain support among UNIX vendors.

985

</p></li><li><p>

986

The mappings of Windows NT RIDs to UNIX IDs is not made algorithmically and depends on the order in

987

which unmapped users or groups are seen by Winbind. It may be difficult to recover the mappings of RID to UNIX

988

ID if the file containing this information is corrupted or destroyed.

989

</p></li><li><p>

990

Currently the Winbind PAM module does not take into account possible workstation and logon time

991

restrictions that may be set for Windows NT users; this is instead up to the PDC to enforce.

992

</p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657374"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>

993

Do not under any circumstances run <code class="literal">nscd</code> on any system

994

on which <code class="literal">winbindd</code> is running.

995

</p></div><p>

996

If <code class="literal">nscd</code> is running on the UNIX/Linux system, then

997

even though NSSWITCH is correctly configured, it will not be possible to resolve

998

domain users and groups for file and directory controls.

999

</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2657411"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p>“<span class="quote">

1000

My <code class="filename">smb.conf</code> file is correctly configured. I have specified <a class="link" href="smb.conf.5.html#IDMAPUID" target="_top">idmap uid = 12000</a>,

1001

and <a class="link" href="smb.conf.5.html#IDMAPGID" target="_top">idmap gid = 3000-3500</a> and <code class="literal">winbind</code> is running.

1002

When I do the following, it all works fine.

1003

</span>”</p><pre class="screen">

1004

<code class="prompt">root# </code><strong class="userinput"><code>wbinfo -u</code></strong>

1005

MIDEARTH\maryo

1006

MIDEARTH\jackb

1007

MIDEARTH\ameds

1008

...

1009

MIDEARTH\root

1010

1011

<code class="prompt">root# </code><strong class="userinput"><code>wbinfo -g</code></strong>

1012

MIDEARTH\Domain Users

1013

MIDEARTH\Domain Admins

1014

MIDEARTH\Domain Guests

1015

...

1016

MIDEARTH\Accounts

1017

1018

<code class="prompt">root# </code><strong class="userinput"><code>getent passwd</code></strong>

1019

root:x:0:0:root:/root:/bin/bash

1020

bin:x:1:1:bin:/bin:/bin/bash

1021

...

1022

maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false

1023

</pre><p>“<span class="quote">

1024

But the following command just fails:

1025

</span>”

1026

</p><pre class="screen">

1027

<code class="prompt">root# </code><strong class="userinput"><code>chown maryo a_file</code></strong>

1028

chown: `maryo': invalid user

1029

</pre><p>

1030

“<span class="quote">

1031

This is driving me nuts! What can be wrong?

1032

</span>”</p><p>

1033

Same problem as the one above.

1034

Your system is likely running <code class="literal">nscd</code>, the name service

1035

caching daemon. Shut it down, do not restart it! You will find your problem resolved.

1036

Alternately, fix the operation of nscd to resolve the problem.

1037

</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="VFS.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="AdvancedNetworkManagement.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�23.�Stackable VFS modules�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�25.�Advanced Network Management</td></tr></table></div></body></html>