Changeset 745 for trunk/server/docs/htmldocs/Samba3-HOWTO/winbind.html
- Timestamp:
- Nov 27, 2012, 4:43:17 PM (13 years ago)
- Location:
- trunk/server
- Files:
-
- 2 edited
-
. (modified) (1 prop)
-
docs/htmldocs/Samba3-HOWTO/winbind.html (modified) (57 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/server
- Property svn:mergeinfo changed
/vendor/current merged: 581,587,591,594,597,600,615,618,740
- Property svn:mergeinfo changed
-
trunk/server/docs/htmldocs/Samba3-HOWTO/winbind.html
r599 r745 1 <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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="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" title="Chapter 24. Winbind: Use of Domain Accounts"><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="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="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="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="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="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#id4172 83">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417609">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417687">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id417826">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id417865">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id417977">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418024">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418102">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418146">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418358">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418499">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418567">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id418617">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418623">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418730">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418872">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id421103">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id421149">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id421183">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id421217">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417283"></a>Features and Benefits</h2></div></div></div><p>2 <a class="indexterm" name="id4172 91"></a>3 <a class="indexterm" name="id4172 97"></a>1 <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.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="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" title="Chapter 24. Winbind: Use of Domain Accounts"><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="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="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="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="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="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#id417272">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417589">Introduction</a></span></dt><dt><span class="sect1"><a href="winbind.html#id417666">What Winbind Provides</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id417805">Target Uses</a></span></dt><dt><span class="sect2"><a href="winbind.html#id417844">Handling of Foreign SIDs</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id417956">How Winbind Works</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418004">Microsoft Remote Procedure Calls</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418082">Microsoft Active Directory Services</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418126">Name Service Switch</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418338">Pluggable Authentication Modules</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418479">User and Group ID Allocation</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418546">Result Caching</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id418597">Installation and Configuration</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id418602">Introduction</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418709">Requirements</a></span></dt><dt><span class="sect2"><a href="winbind.html#id418852">Testing Things Out</a></span></dt></dl></dd><dt><span class="sect1"><a href="winbind.html#id421094">Conclusion</a></span></dt><dt><span class="sect1"><a href="winbind.html#id421140">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="winbind.html#id421173">NSCD Problem Warning</a></span></dt><dt><span class="sect2"><a href="winbind.html#id421207">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417272"></a>Features and Benefits</h2></div></div></div><p> 2 <a class="indexterm" name="id417280"></a> 3 <a class="indexterm" name="id417286"></a> 4 4 Integration of UNIX and Microsoft Windows NT through a unified logon has 5 5 been considered a <span class="quote">“<span class="quote">holy grail</span>”</span> in heterogeneous computing environments for 6 6 a long time. 7 7 </p><p> 8 <a class="indexterm" name="id4173 12"></a>9 <a class="indexterm" name="id4173 19"></a>10 <a class="indexterm" name="id4173 26"></a>11 <a class="indexterm" name="id4173 33"></a>8 <a class="indexterm" name="id417301"></a> 9 <a class="indexterm" name="id417308"></a> 10 <a class="indexterm" name="id417315"></a> 11 <a class="indexterm" name="id417322"></a> 12 12 There is one other facility without which UNIX and Microsoft Windows network 13 13 interoperability would suffer greatly. It is imperative that there be a … … 15 15 domain user and group ownerships with integrity. 16 16 </p><p> 17 <a class="indexterm" name="id4173 45"></a>18 <a class="indexterm" name="id4173 54"></a>19 <a class="indexterm" name="id4173 61"></a>20 <a class="indexterm" name="id4173 68"></a>17 <a class="indexterm" name="id417334"></a> 18 <a class="indexterm" name="id417343"></a> 19 <a class="indexterm" name="id417350"></a> 20 <a class="indexterm" name="id417357"></a> 21 21 <span class="emphasis"><em>winbind</em></span> is a component of the Samba suite of programs that 22 22 solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft … … 28 28 Winbind provides three separate functions: 29 29 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> 30 <a class="indexterm" name="id4173 92"></a>31 <a class="indexterm" name="id4173 98"></a>30 <a class="indexterm" name="id417380"></a> 31 <a class="indexterm" name="id417387"></a> 32 32 Authentication of user credentials (via PAM). This makes it possible to 33 33 log onto a UNIX/Linux system using user and group accounts from a Windows 34 34 NT4 (including a Samba domain) or an Active Directory domain. 35 35 </p></li><li class="listitem"><p> 36 <a class="indexterm" name="id4174 11"></a>37 <a class="indexterm" name="id4174 18"></a>36 <a class="indexterm" name="id417400"></a> 37 <a class="indexterm" name="id417407"></a> 38 38 Identity resolution (via NSS). This is the default when winbind is not used. 39 39 </p></li><li class="listitem"><p> 40 <a class="indexterm" name="id417430"></a> 41 <a class="indexterm" name="id417436"></a> 42 <a class="indexterm" name="id417443"></a> 43 <a class="indexterm" name="id417449"></a> 44 <a class="indexterm" name="id417456"></a> 45 <a class="indexterm" name="id417463"></a> 46 <a class="indexterm" name="id417470"></a> 40 <a class="indexterm" name="id417418"></a> 41 <a class="indexterm" name="id417425"></a> 42 <a class="indexterm" name="id417432"></a> 43 <a class="indexterm" name="id417438"></a> 44 <a class="indexterm" name="id417445"></a> 45 <a class="indexterm" name="id417452"></a> 47 46 Winbind maintains a database called winbind_idmap.tdb in which it stores 48 47 mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only … … 53 52 from the LDAP database. 54 53 </p></li></ul></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 55 <a class="indexterm" name="id417498"></a> 56 <a class="indexterm" name="id417504"></a> 54 <a class="indexterm" name="id417477"></a> 55 <a class="indexterm" name="id417484"></a> 56 <a class="indexterm" name="id417493"></a> 57 <a class="indexterm" name="id417500"></a> 58 <a class="indexterm" name="id417507"></a> 57 59 <a class="indexterm" name="id417514"></a> 58 <a class="indexterm" name="id417520"></a>59 <a class="indexterm" name="id417527"></a>60 <a class="indexterm" name="id417534"></a>61 60 If <code class="literal">winbindd</code> is not running, smbd (which calls <code class="literal">winbindd</code>) will fall back to 62 61 using purely local information from <code class="filename">/etc/passwd</code> and <code class="filename">/etc/group</code> and no dynamic 63 62 mapping will be used. On an operating system that has been enabled with the NSS, 64 63 the resolution of user and group information will be accomplished via NSS. 65 </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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417 609"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have64 </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" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417589"></a>Introduction</h2></div></div></div><p>It is well known that UNIX and Microsoft Windows NT have 66 65 different models for representing user and group information and 67 66 use different technologies for implementing them. This fact has 68 67 made it difficult to integrate the two systems in a satisfactory 69 68 manner.</p><p> 70 <a class="indexterm" name="id4176 23"></a>71 <a class="indexterm" name="id4176 30"></a>69 <a class="indexterm" name="id417602"></a> 70 <a class="indexterm" name="id417609"></a> 72 71 One common solution in use today has been to create 73 72 identically named user accounts on both the UNIX and Windows systems … … 82 81 </p></li><li class="listitem"><p>Password changing for Windows NT users. 83 82 </p></li></ul></div><p> 84 <a class="indexterm" name="id4176 69"></a>85 <a class="indexterm" name="id4176 74"></a>83 <a class="indexterm" name="id417648"></a> 84 <a class="indexterm" name="id417654"></a> 86 85 Ideally, a prospective solution to the unified logon problem 87 86 would satisfy all the above components without duplication of … … 90 89 groups on either system. The Winbind system provides a simple 91 90 and elegant solution to all three components of the unified logon 92 problem.</p></div><div class="sect1" title="What Winbind Provides"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417687"></a>What Winbind Provides</h2></div></div></div><p> 91 problem.</p></div><div class="sect1" title="What Winbind Provides"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417666"></a>What Winbind Provides</h2></div></div></div><p> 92 <a class="indexterm" name="id417674"></a> 93 <a class="indexterm" name="id417681"></a> 94 <a class="indexterm" name="id417688"></a> 93 95 <a class="indexterm" name="id417695"></a> 94 <a class="indexterm" name="id417702"></a>95 <a class="indexterm" name="id417708"></a>96 <a class="indexterm" name="id417715"></a>97 96 Winbind unifies UNIX and Windows NT account management by 98 97 allowing a UNIX box to become a full member of an NT domain. Once … … 101 100 to be used in much the same manner that NIS+ is used within 102 101 UNIX-only environments.</p><p> 103 <a class="indexterm" name="id4177 32"></a>104 <a class="indexterm" name="id4177 39"></a>105 <a class="indexterm" name="id4177 45"></a>106 <a class="indexterm" name="id4177 52"></a>102 <a class="indexterm" name="id417711"></a> 103 <a class="indexterm" name="id417718"></a> 104 <a class="indexterm" name="id417725"></a> 105 <a class="indexterm" name="id417731"></a> 107 106 The end result is that whenever a 108 107 program on the UNIX machine asks the operating system to look up … … 113 112 redirection to the NT domain controller is completely 114 113 transparent.</p><p> 115 <a class="indexterm" name="id4177 66"></a>116 <a class="indexterm" name="id4177 72"></a>114 <a class="indexterm" name="id417745"></a> 115 <a class="indexterm" name="id417752"></a> 117 116 Users on the UNIX machine can then use NT user and group 118 117 names as they would <span class="quote">“<span class="quote">native</span>”</span> UNIX names. They can chown files 119 118 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 <a class="indexterm" name="id4177 88"></a>119 UNIX machine and run a UNIX X Window session as a domain user.</p><p> 120 <a class="indexterm" name="id417768"></a> 122 121 The only obvious indication that Winbind is being used is 123 122 that user and group names take the form <code class="constant">DOMAIN\user</code> and … … 125 124 that redirection to a domain controller is wanted for a particular 126 125 lookup and which trusted domain is being referenced.</p><p> 127 <a class="indexterm" name="id417 808"></a>128 <a class="indexterm" name="id417 815"></a>126 <a class="indexterm" name="id417787"></a> 127 <a class="indexterm" name="id417794"></a> 129 128 Additionally, Winbind provides an authentication service that hooks into the PAM system 130 129 to provide authentication via an NT domain to any PAM-enabled 131 130 applications. This capability solves the problem of synchronizing 132 131 passwords between systems, since all passwords are stored in a single 133 location (on the domain controller).</p><div class="sect2" title="Target Uses"><div class="titlepage"><div><div><h3 class="title"><a name="id4178 26"></a>Target Uses</h3></div></div></div><p>134 <a class="indexterm" name="id4178 33"></a>132 location (on the domain controller).</p><div class="sect2" title="Target Uses"><div class="titlepage"><div><div><h3 class="title"><a name="id417805"></a>Target Uses</h3></div></div></div><p> 133 <a class="indexterm" name="id417813"></a> 135 134 Winbind is targeted at organizations that have an 136 135 existing NT-based domain infrastructure into which they wish … … 140 139 simplifies the administrative overhead of deploying UNIX 141 140 workstations into an NT-based organization.</p><p> 142 <a class="indexterm" name="id4178 47"></a>143 <a class="indexterm" name="id4178 54"></a>141 <a class="indexterm" name="id417826"></a> 142 <a class="indexterm" name="id417833"></a> 144 143 Another interesting way in which we expect Winbind to 145 144 be used is as a central part of UNIX-based appliances. Appliances 146 145 that provide file and print services to Microsoft-based networks 147 146 will be able to use Winbind to provide seamless integration of 148 the appliance into the domain.</p></div><div class="sect2" title="Handling of Foreign SIDs"><div class="titlepage"><div><div><h3 class="title"><a name="id4178 65"></a>Handling of Foreign SIDs</h3></div></div></div><p>149 <a class="indexterm" name="id4178 73"></a>147 the appliance into the domain.</p></div><div class="sect2" title="Handling of Foreign SIDs"><div class="titlepage"><div><div><h3 class="title"><a name="id417844"></a>Handling of Foreign SIDs</h3></div></div></div><p> 148 <a class="indexterm" name="id417852"></a> 150 149 The term <span class="emphasis"><em>foreign SID</em></span> is often met with the reaction that it 151 150 is not relevant to a particular environment. The following documents an interchange … … 153 152 often expressed regarding the use of winbind. 154 153 </p><p> 155 <a class="indexterm" name="id4178 89"></a>154 <a class="indexterm" name="id417868"></a> 156 155 Fact: Winbind is needed to handle users who use workstations that are NOT part 157 156 of the local domain. 158 157 </p><p> 159 <a class="indexterm" name="id417 900"></a>158 <a class="indexterm" name="id417879"></a> 160 159 Response: <span class="quote">“<span class="quote">Why? I've used Samba with workstations that are not part of my domains 161 160 lots of times without using winbind. I thought winbind was for using Samba as a member server 162 161 in a domain controlled by another Samba/Windows PDC.</span>”</span> 163 162 </p><p> 164 <a class="indexterm" name="id417 915"></a>165 <a class="indexterm" name="id4179 22"></a>166 <a class="indexterm" name="id4179 28"></a>163 <a class="indexterm" name="id417895"></a> 164 <a class="indexterm" name="id417901"></a> 165 <a class="indexterm" name="id417908"></a> 167 166 If the Samba server will be accessed from a domain other than the local Samba domain, or 168 167 if there will be access from machines that are not local domain members, winbind will … … 170 169 of the foreign user separate from users that are members of the Samba domain. 171 170 </p><p> 171 <a class="indexterm" name="id417921"></a> 172 <a class="indexterm" name="id417927"></a> 173 <a class="indexterm" name="id417934"></a> 172 174 <a class="indexterm" name="id417941"></a> 173 <a class="indexterm" name="id417948"></a>174 <a class="indexterm" name="id417955"></a>175 <a class="indexterm" name="id417961"></a>176 175 This means that winbind is eminently useful in cases where a single 177 176 Samba PDC on a local network is combined with both domain member and domain non-member workstations. … … 182 181 foreign (non-member of the domain) account will be treated as MACHINE\george because 183 182 each has a different SID. 184 </p></div></div><div class="sect1" title="How Winbind Works"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4179 77"></a>How Winbind Works</h2></div></div></div><p>185 <a class="indexterm" name="id4179 85"></a>186 <a class="indexterm" name="id4179 92"></a>187 <a class="indexterm" name="id4179 98"></a>188 <a class="indexterm" name="id41 8005"></a>183 </p></div></div><div class="sect1" title="How Winbind Works"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417956"></a>How Winbind Works</h2></div></div></div><p> 184 <a class="indexterm" name="id417964"></a> 185 <a class="indexterm" name="id417971"></a> 186 <a class="indexterm" name="id417978"></a> 187 <a class="indexterm" name="id417984"></a> 189 188 The Winbind system is designed around a client/server 190 189 architecture. A long-running <code class="literal">winbindd</code> daemon … … 192 191 to arrive. These requests are generated by the NSS and PAM 193 192 clients and are processed sequentially.</p><p>The technologies used to implement Winbind are described 194 in detail below.</p><div class="sect2" title="Microsoft Remote Procedure Calls"><div class="titlepage"><div><div><h3 class="title"><a name="id4180 24"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p>195 <a class="indexterm" name="id4180 32"></a>196 <a class="indexterm" name="id4180 42"></a>197 <a class="indexterm" name="id4180 48"></a>198 <a class="indexterm" name="id4180 55"></a>199 <a class="indexterm" name="id4180 62"></a>193 in detail below.</p><div class="sect2" title="Microsoft Remote Procedure Calls"><div class="titlepage"><div><div><h3 class="title"><a name="id418004"></a>Microsoft Remote Procedure Calls</h3></div></div></div><p> 194 <a class="indexterm" name="id418012"></a> 195 <a class="indexterm" name="id418021"></a> 196 <a class="indexterm" name="id418028"></a> 197 <a class="indexterm" name="id418034"></a> 198 <a class="indexterm" name="id418041"></a> 200 199 Over the last few years, efforts have been underway by various Samba Team members to implement various aspects of 201 200 the Microsoft Remote Procedure Call (MSRPC) system. This system is used for most network-related operations … … 204 203 Samba, it has also yielded a body of code that can be used for other purposes. 205 204 </p><p> 206 <a class="indexterm" name="id4180 76"></a>207 <a class="indexterm" name="id4180 83"></a>208 <a class="indexterm" name="id4180 90"></a>205 <a class="indexterm" name="id418056"></a> 206 <a class="indexterm" name="id418063"></a> 207 <a class="indexterm" name="id418069"></a> 209 208 Winbind uses various MSRPC calls to enumerate domain users and groups and to obtain detailed information about 210 209 individual users or groups. Other MSRPC calls can be used to authenticate NT domain users and to change user 211 210 passwords. By directly querying a Windows PDC for user and group information, Winbind maps the NT account 212 211 information onto UNIX user and group names. 213 </p></div><div class="sect2" title="Microsoft Active Directory Services"><div class="titlepage"><div><div><h3 class="title"><a name="id418102"></a>Microsoft Active Directory Services</h3></div></div></div><p> 212 </p></div><div class="sect2" title="Microsoft Active Directory Services"><div class="titlepage"><div><div><h3 class="title"><a name="id418082"></a>Microsoft Active Directory Services</h3></div></div></div><p> 213 <a class="indexterm" name="id418090"></a> 214 <a class="indexterm" name="id418096"></a> 215 <a class="indexterm" name="id418103"></a> 214 216 <a class="indexterm" name="id418110"></a> 215 <a class="indexterm" name="id418117"></a>216 <a class="indexterm" name="id418124"></a>217 <a class="indexterm" name="id418130"></a>218 217 Since late 2001, Samba has gained the ability to interact with Microsoft Windows 2000 using its <span class="quote">“<span class="quote">native 219 218 mode</span>”</span> protocols rather than the NT4 RPC services. Using LDAP and Kerberos, a domain member running 220 219 Winbind can enumerate users and groups in exactly the same way as a Windows 200x client would, and in so doing 221 220 provide a much more efficient and effective Winbind implementation. 222 </p></div><div class="sect2" title="Name Service Switch"><div class="titlepage"><div><div><h3 class="title"><a name="id4181 46"></a>Name Service Switch</h3></div></div></div><p>223 <a class="indexterm" name="id4181 54"></a>224 <a class="indexterm" name="id4181 61"></a>225 <a class="indexterm" name="id4181 67"></a>226 <a class="indexterm" name="id4181 74"></a>221 </p></div><div class="sect2" title="Name Service Switch"><div class="titlepage"><div><div><h3 class="title"><a name="id418126"></a>Name Service Switch</h3></div></div></div><p> 222 <a class="indexterm" name="id418134"></a> 223 <a class="indexterm" name="id418140"></a> 224 <a class="indexterm" name="id418147"></a> 225 <a class="indexterm" name="id418153"></a> 227 226 The NSS is a feature that is present in many UNIX operating systems. It allows system 228 227 information such as hostnames, mail aliases, and user information … … 233 232 and then consult an NIS database for user information or a DNS server 234 233 for hostname information.</p><p> 234 <a class="indexterm" name="id418168"></a> 235 <a class="indexterm" name="id418174"></a> 236 <a class="indexterm" name="id418181"></a> 235 237 <a class="indexterm" name="id418188"></a> 236 238 <a class="indexterm" name="id418195"></a> 237 <a class="indexterm" name="id418202"></a>238 <a class="indexterm" name="id418208"></a>239 <a class="indexterm" name="id418215"></a>240 239 The NSS application programming interface allows Winbind to present itself as a source of system 241 240 information when resolving UNIX usernames and groups. Winbind uses this interface and information obtained … … 244 243 groups in an NT domain plus any trusted domain as though they were local users and groups. 245 244 </p><p> 246 <a class="indexterm" name="id4182 30"></a>247 <a class="indexterm" name="id4182 36"></a>248 <a class="indexterm" name="id4182 43"></a>245 <a class="indexterm" name="id418209"></a> 246 <a class="indexterm" name="id418216"></a> 247 <a class="indexterm" name="id418222"></a> 249 248 The primary control file for NSS is <code class="filename">/etc/nsswitch.conf</code>. When a UNIX application 250 249 makes a request to do a lookup, the C library looks in <code class="filename">/etc/nsswitch.conf</code> for a line that … … 255 254 passwd: files example 256 255 </pre><p> 257 <a class="indexterm" name="id4182 74"></a>258 <a class="indexterm" name="id4182 81"></a>259 <a class="indexterm" name="id4182 88"></a>256 <a class="indexterm" name="id418254"></a> 257 <a class="indexterm" name="id418260"></a> 258 <a class="indexterm" name="id418267"></a> 260 259 then the C library will first load a module called <code class="filename">/lib/libnss_files.so</code> followed 261 260 by the module <code class="filename">/lib/libnss_example.so</code>. The C library will dynamically load each of these … … 263 262 is resolved, the C library returns the result to the application. 264 263 </p><p> 265 <a class="indexterm" name="id418 312"></a>266 <a class="indexterm" name="id418 319"></a>267 <a class="indexterm" name="id4183 26"></a>264 <a class="indexterm" name="id418292"></a> 265 <a class="indexterm" name="id418298"></a> 266 <a class="indexterm" name="id418305"></a> 268 267 This NSS interface provides an easy way for Winbind to hook into the operating system. All that needs 269 268 to be done is to put <code class="filename">libnss_winbind.so</code> in <code class="filename">/lib/</code> then add 270 269 <span class="quote">“<span class="quote">winbind</span>”</span> into <code class="filename">/etc/nsswitch.conf</code> at the appropriate place. The C library 271 270 will then call Winbind to resolve user and group names. 272 </p></div><div class="sect2" title="Pluggable Authentication Modules"><div class="titlepage"><div><div><h3 class="title"><a name="id418358"></a>Pluggable Authentication Modules</h3></div></div></div><p> 271 </p></div><div class="sect2" title="Pluggable Authentication Modules"><div class="titlepage"><div><div><h3 class="title"><a name="id418338"></a>Pluggable Authentication Modules</h3></div></div></div><p> 272 <a class="indexterm" name="id418346"></a> 273 <a class="indexterm" name="id418352"></a> 274 <a class="indexterm" name="id418359"></a> 273 275 <a class="indexterm" name="id418366"></a> 274 <a class="indexterm" name="id418373"></a>275 <a class="indexterm" name="id418379"></a>276 <a class="indexterm" name="id418386"></a>277 276 PAMs provide a system for abstracting authentication and authorization technologies. With a PAM 278 277 module, it is possible to specify different authentication methods for different system applications without … … 281 280 local password file but only allow users resolved from an NIS database to log in over the network. 282 281 </p><p> 283 <a class="indexterm" name="id418401"></a> 282 <a class="indexterm" name="id418380"></a> 283 <a class="indexterm" name="id418387"></a> 284 <a class="indexterm" name="id418394"></a> 285 <a class="indexterm" name="id418400"></a> 284 286 <a class="indexterm" name="id418407"></a> 285 <a class="indexterm" name="id418414"></a>286 <a class="indexterm" name="id418421"></a>287 <a class="indexterm" name="id418428"></a>288 287 Winbind uses the authentication management and password management PAM interface to integrate Windows 289 288 NT users into a UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated … … 291 290 on the PDC. 292 291 </p><p> 292 <a class="indexterm" name="id418420"></a> 293 <a class="indexterm" name="id418426"></a> 294 <a class="indexterm" name="id418433"></a> 293 295 <a class="indexterm" name="id418440"></a> 294 <a class="indexterm" name="id418447"></a>295 <a class="indexterm" name="id418454"></a>296 <a class="indexterm" name="id418461"></a>297 296 PAM is configured by providing control files in the directory <code class="filename">/etc/pam.d/</code> for 298 297 each of the services that require authentication. When an authentication request is made by an application, … … 302 301 and the PAM control files for relevant services are updated to allow authentication via Winbind. See the PAM 303 302 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" title="User and Group ID Allocation"><div class="titlepage"><div><div><h3 class="title"><a name="id4184 99"></a>User and Group ID Allocation</h3></div></div></div><p>305 <a class="indexterm" name="id418 507"></a>306 <a class="indexterm" name="id418 513"></a>307 <a class="indexterm" name="id4185 20"></a>303 </p></div><div class="sect2" title="User and Group ID Allocation"><div class="titlepage"><div><div><h3 class="title"><a name="id418479"></a>User and Group ID Allocation</h3></div></div></div><p> 304 <a class="indexterm" name="id418486"></a> 305 <a class="indexterm" name="id418493"></a> 306 <a class="indexterm" name="id418500"></a> 308 307 When a user or group is created under Windows NT/200x, it is allocated a numerical relative identifier 309 308 (RID). This is slightly different from UNIX, which has a range of numbers that are used to identify users and … … 314 313 will have mapped all Windows NT users and groups to UNIX user IDs and group IDs. 315 314 </p><p> 315 <a class="indexterm" name="id418516"></a> 316 <a class="indexterm" name="id418523"></a> 317 <a class="indexterm" name="id418529"></a> 316 318 <a class="indexterm" name="id418536"></a> 317 <a class="indexterm" name="id418543"></a>318 <a class="indexterm" name="id418550"></a>319 <a class="indexterm" name="id418557"></a>320 319 The results of this mapping are stored persistently in an ID mapping database held in a tdb database. 321 320 This ensures that RIDs are mapped to UNIX IDs in a consistent way. 322 </p></div><div class="sect2" title="Result Caching"><div class="titlepage"><div><div><h3 class="title"><a name="id418567"></a>Result Caching</h3></div></div></div><p> 323 <a class="indexterm" name="id418575"></a> 321 </p></div><div class="sect2" title="Result Caching"><div class="titlepage"><div><div><h3 class="title"><a name="id418546"></a>Result Caching</h3></div></div></div><p> 322 <a class="indexterm" name="id418554"></a> 323 <a class="indexterm" name="id418561"></a> 324 <a class="indexterm" name="id418567"></a> 325 <a class="indexterm" name="id418574"></a> 324 326 <a class="indexterm" name="id418581"></a> 325 <a class="indexterm" name="id418588"></a>326 <a class="indexterm" name="id418595"></a>327 <a class="indexterm" name="id418601"></a>328 327 An active directory system can generate a lot of user and group name lookups. To reduce the network 329 328 cost of these lookups, Winbind uses a caching scheme based on the SAM sequence number supplied by NT domain … … 333 332 compared against the sequence number of the cached entry. If the sequence numbers do not match, then the 334 333 cached information is discarded and up-to-date information is requested directly from the PDC. 335 </p></div></div><div class="sect1" title="Installation and Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id418 617"></a>Installation and Configuration</h2></div></div></div><div class="sect2" title="Introduction"><div class="titlepage"><div><div><h3 class="title"><a name="id418623"></a>Introduction</h3></div></div></div><p>336 <a class="indexterm" name="id4186 31"></a>337 <a class="indexterm" name="id4186 38"></a>338 <a class="indexterm" name="id4186 44"></a>334 </p></div></div><div class="sect1" title="Installation and Configuration"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id418597"></a>Installation and Configuration</h2></div></div></div><div class="sect2" title="Introduction"><div class="titlepage"><div><div><h3 class="title"><a name="id418602"></a>Introduction</h3></div></div></div><p> 335 <a class="indexterm" name="id418610"></a> 336 <a class="indexterm" name="id418617"></a> 337 <a class="indexterm" name="id418624"></a> 339 338 This section describes the procedures used to get Winbind up and running. Winbind is capable of providing 340 339 access and authentication control for Windows Domain users through an NT or Windows 200x PDC for regular … … 343 342 <span class="emphasis"><em>Why should I do this?</em></span> 344 343 </p><p> 344 <a class="indexterm" name="id418647"></a> 345 <a class="indexterm" name="id418654"></a> 346 <a class="indexterm" name="id418661"></a> 345 347 <a class="indexterm" name="id418667"></a> 346 <a class="indexterm" name="id418674"></a>347 <a class="indexterm" name="id418681"></a>348 <a class="indexterm" name="id418688"></a>349 348 This allows the Samba administrator to rely on the authentication mechanisms on the Windows NT/200x PDC 350 349 for the authentication of domain members. Windows NT/200x users no longer need to have separate accounts on … … 353 352 <span class="emphasis"><em>Who should be reading this document?</em></span> 354 353 </p><p> 355 <a class="indexterm" name="id418 710"></a>356 <a class="indexterm" name="id418 717"></a>354 <a class="indexterm" name="id418690"></a> 355 <a class="indexterm" name="id418696"></a> 357 356 This document is designed for system administrators. If you are implementing Samba on a file server and wish 358 357 to (fairly easily) integrate existing Windows NT/200x users from your PDC onto the Samba server, this document 359 358 is for you. 360 </p></li></ul></div></div><div class="sect2" title="Requirements"><div class="titlepage"><div><div><h3 class="title"><a name="id4187 30"></a>Requirements</h3></div></div></div><p>361 <a class="indexterm" name="id4187 38"></a>362 <a class="indexterm" name="id4187 44"></a>363 <a class="indexterm" name="id4187 51"></a>359 </p></li></ul></div></div><div class="sect2" title="Requirements"><div class="titlepage"><div><div><h3 class="title"><a name="id418709"></a>Requirements</h3></div></div></div><p> 360 <a class="indexterm" name="id418717"></a> 361 <a class="indexterm" name="id418724"></a> 362 <a class="indexterm" name="id418730"></a> 364 363 If you have a Samba configuration file that you are currently using, <span class="emphasis"><em>BACK IT UP!</em></span> 365 364 If your system already uses PAM, <span class="emphasis"><em>back up the <code class="filename">/etc/pam.d</code> directory 366 365 contents!</em></span> If you haven't already made a boot disk, <span class="emphasis"><em>MAKE ONE NOW!</em></span> 367 366 </p><p> 368 <a class="indexterm" name="id4187 79"></a>369 <a class="indexterm" name="id4187 86"></a>370 <a class="indexterm" name="id4187 92"></a>367 <a class="indexterm" name="id418758"></a> 368 <a class="indexterm" name="id418765"></a> 369 <a class="indexterm" name="id418772"></a> 371 370 Messing with the PAM configuration files can make it nearly impossible to log in to your machine. That's 372 371 why you want to be able to boot back into your machine in single-user mode and restore your … … 374 373 way things are going. 375 374 </p><p> 376 <a class="indexterm" name="id418 811"></a>377 <a class="indexterm" name="id418 818"></a>375 <a class="indexterm" name="id418790"></a> 376 <a class="indexterm" name="id418797"></a> 378 377 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 378 instructions on downloading the source code. 380 379 </p><p> 380 <a class="indexterm" name="id418815"></a> 381 <a class="indexterm" name="id418821"></a> 382 <a class="indexterm" name="id418828"></a> 381 383 <a class="indexterm" name="id418835"></a> 382 <a class="indexterm" name="id418842"></a>383 <a class="indexterm" name="id418849"></a>384 <a class="indexterm" name="id418855"></a>385 384 To allow domain users the ability to access Samba shares and files, as well as potentially other services 386 385 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" title="Testing Things Out"><div class="titlepage"><div><div><h3 class="title"><a name="id418872"></a>Testing Things Out</h3></div></div></div><p> 386 machine. In order to compile the Winbind modules, the PAM development libraries should be installed 387 on your system. Please refer to the <a class="ulink" href="http://www.kernel.org/pub/linux/libs/pam/" target="_top">PAM Web Site</a>. 388 </p></div><div class="sect2" title="Testing Things Out"><div class="titlepage"><div><div><h3 class="title"><a name="id418852"></a>Testing Things Out</h3></div></div></div><p> 389 <a class="indexterm" name="id418860"></a> 390 <a class="indexterm" name="id418867"></a> 391 <a class="indexterm" name="id418874"></a> 390 392 <a class="indexterm" name="id418880"></a> 391 <a class="indexterm" name="id418886"></a> 392 <a class="indexterm" name="id418893"></a> 393 <a class="indexterm" name="id418900"></a> 394 <a class="indexterm" name="id418907"></a> 393 <a class="indexterm" name="id418887"></a> 395 394 Before starting, it is probably best to kill off all the Samba-related daemons running on your server. 396 395 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, … … 400 399 better in Samba if the pam-devel package is also installed. This package includes the header files 401 400 needed to compile PAM-aware applications. 402 </p><div class="sect3" title="Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris"><div class="titlepage"><div><div><h4 class="title"><a name="id4189 54"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p>403 <a class="indexterm" name="id4189 68"></a>404 <a class="indexterm" name="id4189 75"></a>405 <a class="indexterm" name="id4189 81"></a>406 <a class="indexterm" name="id4189 88"></a>401 </p><div class="sect3" title="Configure nsswitch.conf and the Winbind Libraries on Linux and Solaris"><div class="titlepage"><div><div><h4 class="title"><a name="id418935"></a>Configure <code class="filename">nsswitch.conf</code> and the Winbind Libraries on Linux and Solaris</h4></div></div></div><p> 402 <a class="indexterm" name="id418949"></a> 403 <a class="indexterm" name="id418955"></a> 404 <a class="indexterm" name="id418962"></a> 405 <a class="indexterm" name="id418969"></a> 407 406 PAM is a standard component of most current generation UNIX/Linux systems. Unfortunately, few systems install 408 407 the <code class="filename">pam-devel</code> libraries that are needed to build PAM-enabled Samba. Additionally, Samba-3 … … 414 413 The libraries needed to run the <span class="application">winbindd</span> daemon through nsswitch need to be copied to their proper locations: 415 414 </p><p> 416 <a class="indexterm" name="id4190 23"></a>415 <a class="indexterm" name="id419004"></a> 417 416 </p><pre class="screen"> 418 417 <code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/libnss_winbind.so /lib</code></strong> … … 423 422 <code class="prompt">root# </code> <strong class="userinput"><code>ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</code></strong> 424 423 </p><p>And, in the case of Sun Solaris: 425 <a class="indexterm" name="id4190 69"></a>424 <a class="indexterm" name="id419049"></a> 426 425 </p><pre class="screen"> 427 426 <code class="prompt">root# </code><strong class="userinput"><code>ln -s /usr/lib/libnss_winbind.so /usr/lib/libnss_winbind.so.1</code></strong> … … 430 429 </pre><p> 431 430 </p><p> 432 <a class="indexterm" name="id419 117"></a>431 <a class="indexterm" name="id419097"></a> 433 432 As root, edit <code class="filename">/etc/nsswitch.conf</code> to allow user and group entries to be visible from the 434 433 <span class="application">winbindd</span> daemon. My <code class="filename">/etc/nsswitch.conf</code> file looked like this after editing: … … 438 437 group: files winbind 439 438 </pre><p> 440 <a class="indexterm" name="id4191 50"></a>441 <a class="indexterm" name="id4191 57"></a>442 <a class="indexterm" name="id4191 64"></a>443 <a class="indexterm" name="id4191 71"></a>444 <a class="indexterm" name="id4191 78"></a>439 <a class="indexterm" name="id419131"></a> 440 <a class="indexterm" name="id419138"></a> 441 <a class="indexterm" name="id419145"></a> 442 <a class="indexterm" name="id419151"></a> 443 <a class="indexterm" name="id419158"></a> 445 444 The libraries needed by the <code class="literal">winbindd</code> daemon will be automatically 446 445 entered into the <code class="literal">ldconfig</code> cache the next time … … 454 453 this library is indeed recognized by the dynamic link loader. 455 454 </p><p> 456 <a class="indexterm" name="id4192 37"></a>457 <a class="indexterm" name="id4192 44"></a>458 <a class="indexterm" name="id4192 51"></a>459 <a class="indexterm" name="id4192 57"></a>460 <a class="indexterm" name="id4192 64"></a>455 <a class="indexterm" name="id419218"></a> 456 <a class="indexterm" name="id419224"></a> 457 <a class="indexterm" name="id419231"></a> 458 <a class="indexterm" name="id419238"></a> 459 <a class="indexterm" name="id419245"></a> 461 460 The Sun Solaris dynamic link loader management tool is called <code class="literal">crle</code>. The 462 461 use of this tool is necessary to instruct the dynamic link loader to search directories that … … 481 480 From this it is apparent that the <code class="filename">/usr/local/lib</code> directory is included 482 481 in the search dynamic link libraries in order to satisfy object module dependencies. 483 </p></div><div class="sect3" title="NSS Winbind on AIX"><div class="titlepage"><div><div><h4 class="title"><a name="id4193 28"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p>484 <a class="indexterm" name="id4193 39"></a>485 <a class="indexterm" name="id4193 46"></a>486 <a class="indexterm" name="id4193 53"></a>487 <a class="indexterm" name="id4193 59"></a>488 <a class="indexterm" name="id4193 66"></a>489 <a class="indexterm" name="id4193 73"></a>482 </p></div><div class="sect3" title="NSS Winbind on AIX"><div class="titlepage"><div><div><h4 class="title"><a name="id419308"></a>NSS Winbind on AIX</h4></div></div></div><p>(This section is only for those running AIX.)</p><p> 483 <a class="indexterm" name="id419320"></a> 484 <a class="indexterm" name="id419326"></a> 485 <a class="indexterm" name="id419333"></a> 486 <a class="indexterm" name="id419340"></a> 487 <a class="indexterm" name="id419347"></a> 488 <a class="indexterm" name="id419354"></a> 490 489 The Winbind AIX identification module gets built as <code class="filename">libnss_winbind.so</code> in the 491 490 nsswitch directory of the Samba source. This file can be copied to <code class="filename">/usr/lib/security</code>, … … 505 504 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 505 Management Guide: Operating System and Devices.</a> 507 </p></div><div class="sect3" title="Configure smb.conf"><div class="titlepage"><div><div><h4 class="title"><a name="id4194 30"></a>Configure smb.conf</h4></div></div></div><p>508 <a class="indexterm" name="id4194 38"></a>509 <a class="indexterm" name="id4194 44"></a>510 <a class="indexterm" name="id4194 51"></a>506 </p></div><div class="sect3" title="Configure smb.conf"><div class="titlepage"><div><div><h4 class="title"><a name="id419410"></a>Configure smb.conf</h4></div></div></div><p> 507 <a class="indexterm" name="id419418"></a> 508 <a class="indexterm" name="id419425"></a> 509 <a class="indexterm" name="id419432"></a> 511 510 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 511 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 border="0" summary="Simple list" class="simplelist"><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="id4195 22"></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="id419538"></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="id419553"></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="id419568"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id419580"></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="id419595"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id419607"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" title="Join the Samba Server to the PDC Domain"><div class="titlepage"><div><div><h4 class="title"><a name="id419620"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p>514 <a class="indexterm" name="id4196 28"></a>515 <a class="indexterm" name="id4196 35"></a>516 <a class="indexterm" name="id4196 42"></a>512 </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 border="0" summary="Simple list" class="simplelist"><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="id419503"></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="id419518"></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="id419533"></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="id419548"></a><em class="parameter"><code>winbind enum users = yes</code></em></td></tr><tr><td><a class="indexterm" name="id419560"></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="id419576"></a><em class="parameter"><code>template homedir = /home/winnt/%D/%U</code></em></td></tr><tr><td><a class="indexterm" name="id419587"></a><em class="parameter"><code>template shell = /bin/bash</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" title="Join the Samba Server to the PDC Domain"><div class="titlepage"><div><div><h4 class="title"><a name="id419601"></a>Join the Samba Server to the PDC Domain</h4></div></div></div><p> 513 <a class="indexterm" name="id419609"></a> 514 <a class="indexterm" name="id419616"></a> 515 <a class="indexterm" name="id419622"></a> 517 516 All machines that will participate in domain security should be members of 518 517 the domain. This applies also to the PDC and all BDCs. 519 518 </p><p> 520 <a class="indexterm" name="id4196 53"></a>521 <a class="indexterm" name="id4196 59"></a>522 <a class="indexterm" name="id4196 66"></a>523 <a class="indexterm" name="id4196 77"></a>524 <a class="indexterm" name="id4196 84"></a>525 <a class="indexterm" name="id4196 91"></a>526 <a class="indexterm" name="id4196 97"></a>527 <a class="indexterm" name="id419 704"></a>528 <a class="indexterm" name="id419 711"></a>519 <a class="indexterm" name="id419633"></a> 520 <a class="indexterm" name="id419640"></a> 521 <a class="indexterm" name="id419647"></a> 522 <a class="indexterm" name="id419658"></a> 523 <a class="indexterm" name="id419665"></a> 524 <a class="indexterm" name="id419671"></a> 525 <a class="indexterm" name="id419678"></a> 526 <a class="indexterm" name="id419685"></a> 527 <a class="indexterm" name="id419692"></a> 529 528 The process of joining a domain requires the use of the <code class="literal">net rpc join</code> 530 529 command. This process communicates with the domain controller it will register with … … 533 532 start Samba on a PDC so that it can join its own domain. 534 533 </p><p> 535 <a class="indexterm" name="id4197 36"></a>536 <a class="indexterm" name="id4197 42"></a>537 <a class="indexterm" name="id4197 49"></a>534 <a class="indexterm" name="id419716"></a> 535 <a class="indexterm" name="id419723"></a> 536 <a class="indexterm" name="id419730"></a> 538 537 Enter the following command to make the Samba server join the domain, where <em class="replaceable"><code>PDC</code></em> is 539 538 the name of your PDC and <em class="replaceable"><code>Administrator</code></em> is a domain user who has administrative 540 539 privileges in the domain. 541 540 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 541 <a class="indexterm" name="id419749"></a> 542 <a class="indexterm" name="id419756"></a> 543 <a class="indexterm" name="id419763"></a> 542 544 <a class="indexterm" name="id419769"></a> 543 <a class="indexterm" name="id419776"></a>544 <a class="indexterm" name="id419782"></a>545 <a class="indexterm" name="id419789"></a>546 545 Before attempting to join a machine to the domain, verify that Samba is running 547 546 on the target domain controller (usually PDC) and that it is capable of being reached via ports 548 547 137/udp, 135/tcp, 139/tcp, and 445/tcp (if Samba or Windows Server 2Kx). 549 548 </p></div><p> 550 <a class="indexterm" name="id419 801"></a>549 <a class="indexterm" name="id419782"></a> 551 550 The use of the <code class="literal">net rpc join</code> facility is shown here: 552 551 </p><pre class="screen"> … … 556 555 <em class="replaceable"><code>DOMAIN</code></em></span>”</span> where <em class="replaceable"><code>DOMAIN</code></em> 557 556 is your domain name. 558 </p></div><div class="sect3" title="Starting and Testing the winbindd Daemon"><div class="titlepage"><div><div><h4 class="title"><a name="id4198 47"></a>Starting and Testing the <code class="literal">winbindd</code> Daemon</h4></div></div></div><p>559 <a class="indexterm" name="id4198 61"></a>560 <a class="indexterm" name="id4198 68"></a>561 <a class="indexterm" name="id4198 75"></a>557 </p></div><div class="sect3" title="Starting and Testing the winbindd Daemon"><div class="titlepage"><div><div><h4 class="title"><a name="id419828"></a>Starting and Testing the <code class="literal">winbindd</code> Daemon</h4></div></div></div><p> 558 <a class="indexterm" name="id419842"></a> 559 <a class="indexterm" name="id419849"></a> 560 <a class="indexterm" name="id419855"></a> 562 561 Eventually, you will want to modify your Samba startup script to automatically invoke the winbindd daemon when 563 562 the other parts of Samba start, but it is possible to test out just the Winbind portion first. To start up … … 568 567 Use the appropriate path to the location of the <code class="literal">winbindd</code> executable file. 569 568 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 570 <a class="indexterm" name="id419 911"></a>571 <a class="indexterm" name="id419 918"></a>569 <a class="indexterm" name="id419891"></a> 570 <a class="indexterm" name="id419898"></a> 572 571 The command to start up Winbind services assumes that Samba has been installed in the 573 572 <code class="filename">/usr/local/samba</code> directory tree. You may need to search for the location of Samba files 574 573 if this is not the location of <code class="literal">winbindd</code> on your system. 575 574 </p></div><p> 576 <a class="indexterm" name="id4199 41"></a>577 <a class="indexterm" name="id4199 48"></a>575 <a class="indexterm" name="id419922"></a> 576 <a class="indexterm" name="id419928"></a> 578 577 I'm always paranoid and like to make sure the daemon is really running. 579 578 </p><pre class="screen"> … … 581 580 </pre><p> 582 581 </p><p> 583 <a class="indexterm" name="id4199 75"></a>582 <a class="indexterm" name="id419955"></a> 584 583 This command should produce output like the following if the daemon is running. 585 584 </p><pre class="screen"> … … 587 586 </pre><p> 588 587 </p><p> 589 <a class="indexterm" name="id4199 91"></a>590 <a class="indexterm" name="id4199 98"></a>588 <a class="indexterm" name="id419972"></a> 589 <a class="indexterm" name="id419978"></a> 591 590 Now, for the real test, try to get some information about the users on your PDC: 592 591 </p><pre class="screen"> … … 606 605 <span class="quote">“<span class="quote">\</span>”</span>. 607 606 </p><p> 608 <a class="indexterm" name="id4200 52"></a>609 <a class="indexterm" name="id4200 59"></a>607 <a class="indexterm" name="id420032"></a> 608 <a class="indexterm" name="id420039"></a> 610 609 You can do the same sort of thing to get group information from the PDC: 611 610 </p><pre class="screen"> … … 621 620 CEO\Group Policy Creator Owners 622 621 </pre><p> 623 <a class="indexterm" name="id420085"></a> 622 <a class="indexterm" name="id420066"></a> 623 <a class="indexterm" name="id420072"></a> 624 <a class="indexterm" name="id420079"></a> 625 <a class="indexterm" name="id420086"></a> 624 626 <a class="indexterm" name="id420092"></a> 625 <a class="indexterm" name="id420098"></a> 626 <a class="indexterm" name="id420105"></a> 627 <a class="indexterm" name="id420112"></a> 628 <a class="indexterm" name="id420118"></a> 629 <a class="indexterm" name="id420125"></a> 627 <a class="indexterm" name="id420099"></a> 628 <a class="indexterm" name="id420106"></a> 630 629 The function <code class="literal">getent</code> can now be used to get unified lists of both local and PDC users and 631 630 groups. Try the following command: … … 641 640 <code class="prompt">root# </code><strong class="userinput"><code>getent group</code></strong> 642 641 </pre><p> 643 </p></div><div class="sect3" title="Fix the init.d Startup Scripts"><div class="titlepage"><div><div><h4 class="title"><a name="id420184"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" title="Linux"><div class="titlepage"><div><div><h5 class="title"><a name="id420190"></a>Linux</h5></div></div></div><p> 644 <a class="indexterm" name="id420197"></a> 645 <a class="indexterm" name="id420204"></a> 646 <a class="indexterm" name="id420211"></a> 647 <a class="indexterm" name="id420218"></a> 648 <a class="indexterm" name="id420224"></a> 649 <a class="indexterm" name="id420231"></a> 650 <a class="indexterm" name="id420238"></a> 651 <a class="indexterm" name="id420244"></a> 652 <a class="indexterm" name="id420249"></a> 642 </p></div><div class="sect3" title="Fix the init.d Startup Scripts"><div class="titlepage"><div><div><h4 class="title"><a name="id420164"></a>Fix the init.d Startup Scripts</h4></div></div></div><div class="sect4" title="Linux"><div class="titlepage"><div><div><h5 class="title"><a name="id420170"></a>Linux</h5></div></div></div><p> 643 <a class="indexterm" name="id420178"></a> 644 <a class="indexterm" name="id420185"></a> 645 <a class="indexterm" name="id420191"></a> 646 <a class="indexterm" name="id420198"></a> 647 <a class="indexterm" name="id420205"></a> 648 <a class="indexterm" name="id420212"></a> 653 649 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 650 task, you need to modify the startup scripts of your system. They are located at … … 711 707 return $RETVAL 712 708 } 713 </pre></div><div class="sect4" title="Solaris"><div class="titlepage"><div><div><h5 class="title"><a name="id4203 73"></a>Solaris</h5></div></div></div><p>709 </pre></div><div class="sect4" title="Solaris"><div class="titlepage"><div><div><h5 class="title"><a name="id420337"></a>Solaris</h5></div></div></div><p> 714 710 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 711 for details. 716 712 </p><p> 717 <a class="indexterm" name="id4203 92"></a>718 <a class="indexterm" name="id4203 99"></a>719 <a class="indexterm" name="id420 406"></a>720 <a class="indexterm" name="id420 413"></a>721 <a class="indexterm" name="id420 420"></a>722 <a class="indexterm" name="id420 426"></a>713 <a class="indexterm" name="id420356"></a> 714 <a class="indexterm" name="id420363"></a> 715 <a class="indexterm" name="id420370"></a> 716 <a class="indexterm" name="id420377"></a> 717 <a class="indexterm" name="id420384"></a> 718 <a class="indexterm" name="id420390"></a> 723 719 On Solaris, you need to modify the <code class="filename">/etc/init.d/samba.server</code> startup script. It 724 720 usually only starts smbd and nmbd but should now start winbindd, too. If you have Samba installed in … … 773 769 esac 774 770 </pre><p> 775 Again, if you would like to run Sambain dual daemon mode, replace:771 Again, if you would like to run winbindd in dual daemon mode, replace: 776 772 </p><pre class="programlisting"> 777 773 /usr/local/samba/sbin/winbindd … … 781 777 /usr/local/samba/sbin/winbindd -D 782 778 </pre><p> 783 </p></div><div class="sect4" title="Restarting"><div class="titlepage"><div><div><h5 class="title"><a name="id4204 92"></a>Restarting</h5></div></div></div><p>784 <a class="indexterm" name="id420 500"></a>785 <a class="indexterm" name="id420 507"></a>779 </p></div><div class="sect4" title="Restarting"><div class="titlepage"><div><div><h5 class="title"><a name="id420456"></a>Restarting</h5></div></div></div><p> 780 <a class="indexterm" name="id420464"></a> 781 <a class="indexterm" name="id420471"></a> 786 782 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 783 should be able to connect to the Samba server as a domain member just as 788 784 if you were a local user. 789 </p></div></div><div class="sect3" title="Configure Winbind and PAM"><div class="titlepage"><div><div><h4 class="title"><a name="id4205 36"></a>Configure Winbind and PAM</h4></div></div></div><p>790 <a class="indexterm" name="id4205 43"></a>791 <a class="indexterm" name="id4205 50"></a>792 <a class="indexterm" name="id4205 57"></a>793 <a class="indexterm" name="id4205 64"></a>785 </p></div></div><div class="sect3" title="Configure Winbind and PAM"><div class="titlepage"><div><div><h4 class="title"><a name="id420500"></a>Configure Winbind and PAM</h4></div></div></div><p> 786 <a class="indexterm" name="id420508"></a> 787 <a class="indexterm" name="id420514"></a> 788 <a class="indexterm" name="id420521"></a> 789 <a class="indexterm" name="id420528"></a> 794 790 If you have made it this far, you know that <code class="literal">winbindd</code> and Samba are working together. If you 795 791 want to use Winbind to provide authentication for other services, keep reading. The PAM configuration files … … 797 793 <code class="filename">/etc/pam.d</code> files? If not, do it now.) 798 794 </p><p> 799 <a class="indexterm" name="id4205 88"></a>800 <a class="indexterm" name="id4205 95"></a>801 <a class="indexterm" name="id420 601"></a>802 <a class="indexterm" name="id420 608"></a>803 <a class="indexterm" name="id420 615"></a>804 <a class="indexterm" name="id420 622"></a>795 <a class="indexterm" name="id420552"></a> 796 <a class="indexterm" name="id420559"></a> 797 <a class="indexterm" name="id420566"></a> 798 <a class="indexterm" name="id420572"></a> 799 <a class="indexterm" name="id420579"></a> 800 <a class="indexterm" name="id420586"></a> 805 801 You will need a PAM module to use winbindd with these other services. This module will be compiled in the 806 802 <code class="filename">../source/nsswitch</code> directory by invoking the command: … … 815 811 <code class="prompt">root# </code><strong class="userinput"><code>cp ../samba/source/nsswitch/pam_winbind.so /lib/security</code></strong> 816 812 </pre><p> 817 </p><div class="sect4" title="Linux/FreeBSD-Specific PAM Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id4206 94"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p>818 <a class="indexterm" name="id420 702"></a>813 </p><div class="sect4" title="Linux/FreeBSD-Specific PAM Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id420659"></a>Linux/FreeBSD-Specific PAM Configuration</h5></div></div></div><p> 814 <a class="indexterm" name="id420667"></a> 819 815 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 816 </p><pre class="programlisting"> … … 822 818 account required /lib/security/pam_stack.so service=system-auth 823 819 </pre><p> 824 <a class="indexterm" name="id420 725"></a>825 <a class="indexterm" name="id420 731"></a>826 <a class="indexterm" name="id4207 38"></a>827 <a class="indexterm" name="id4207 45"></a>828 <a class="indexterm" name="id4207 52"></a>829 <a class="indexterm" name="id4207 59"></a>830 <a class="indexterm" name="id4207 65"></a>831 <a class="indexterm" name="id4207 72"></a>832 <a class="indexterm" name="id4207 79"></a>820 <a class="indexterm" name="id420689"></a> 821 <a class="indexterm" name="id420696"></a> 822 <a class="indexterm" name="id420702"></a> 823 <a class="indexterm" name="id420709"></a> 824 <a class="indexterm" name="id420716"></a> 825 <a class="indexterm" name="id420723"></a> 826 <a class="indexterm" name="id420730"></a> 827 <a class="indexterm" name="id420736"></a> 828 <a class="indexterm" name="id420743"></a> 833 829 The other services that I modified to allow the use of Winbind as an authentication service were the normal 834 830 login on the console (or a terminal session), telnet logins, and ftp service. In order to enable these … … 844 840 enable = yes 845 841 </pre><p> 846 <a class="indexterm" name="id420 827"></a>847 <a class="indexterm" name="id420 834"></a>848 <a class="indexterm" name="id4208 40"></a>842 <a class="indexterm" name="id420791"></a> 843 <a class="indexterm" name="id420798"></a> 844 <a class="indexterm" name="id420805"></a> 849 845 For ftp services to work properly, you will also need to either have individual directories for the domain 850 846 users already present on the server or change the home directory template to a general directory for all 851 847 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 848 </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 853 <a class="indexterm" name="id4208 73"></a>849 <a class="indexterm" name="id420837"></a> 854 850 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 851 pre-create the directories of users to make sure users can log in on UNIX with their own home directory. 856 852 </p></div><p> 857 <a class="indexterm" name="id4208 95"></a>858 <a class="indexterm" name="id420 901"></a>859 <a class="indexterm" name="id420 908"></a>853 <a class="indexterm" name="id420859"></a> 854 <a class="indexterm" name="id420865"></a> 855 <a class="indexterm" name="id420872"></a> 860 856 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:857 the <code class="filename">/etc/pam.d/samba</code>Samba file. My <code class="filename">/etc/pam.d/ftp</code> file was changed to look like this: 862 858 </p><pre class="programlisting"> 863 859 auth required /lib/security/pam_listfile.so item=user sense=deny \ … … 870 866 session required /lib/security/pam_stack.so service=system-auth 871 867 </pre><p> 872 <a class="indexterm" name="id4209 40"></a>868 <a class="indexterm" name="id420909"></a> 873 869 The <code class="filename">/etc/pam.d/login</code> file can be changed in nearly the same way. It now looks like this: 874 870 </p><pre class="programlisting"> … … 884 880 session optional /lib/security/pam_console.so 885 881 </pre><p> 886 <a class="indexterm" name="id4209 64"></a>887 <a class="indexterm" name="id4209 71"></a>888 <a class="indexterm" name="id4209 77"></a>882 <a class="indexterm" name="id420933"></a> 883 <a class="indexterm" name="id420940"></a> 884 <a class="indexterm" name="id420947"></a> 889 885 In this case, I added the </p><pre class="programlisting">auth sufficient /lib/security/pam_winbind.so</pre><p> lines 890 886 as before, but also added the </p><pre class="programlisting">required pam_securetty.so</pre><p> above it to disallow … … 892 888 use_first_pass</pre><p> line after the <code class="literal">winbind.so</code> line to get rid of annoying 893 889 double prompts for passwords. 894 </p></div><div class="sect4" title="Solaris-Specific Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id42 1012"></a>Solaris-Specific Configuration</h5></div></div></div><p>895 <a class="indexterm" name="id42 1020"></a>896 <a class="indexterm" name="id42 1027"></a>890 </p></div><div class="sect4" title="Solaris-Specific Configuration"><div class="titlepage"><div><div><h5 class="title"><a name="id420982"></a>Solaris-Specific Configuration</h5></div></div></div><p> 891 <a class="indexterm" name="id420990"></a> 892 <a class="indexterm" name="id420996"></a> 897 893 The <code class="filename">/etc/pam.conf</code> needs to be changed. I changed this file so my Domain 898 894 users can log on both locally as well as with telnet. The following are the changes … … 961 957 #other password optional /usr/lib/security/$ISA/pam_krb5.so.1 try_first_pass 962 958 </pre><p> 963 <a class="indexterm" name="id4210 75"></a>959 <a class="indexterm" name="id421065"></a> 964 960 I also added a <em class="parameter"><code>try_first_pass</code></em> line after the <code class="filename">winbind.so</code> 965 961 line to get rid of annoying double prompts for passwords. … … 967 963 Now restart your Samba and try connecting through your application that you 968 964 configured in the pam.conf. 969 </p></div></div></div></div><div class="sect1" title="Conclusion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id421 103"></a>Conclusion</h2></div></div></div><p>970 <a class="indexterm" name="id4211 11"></a>971 <a class="indexterm" name="id4211 18"></a>972 <a class="indexterm" name="id4211 24"></a>973 <a class="indexterm" name="id4211 31"></a>974 <a class="indexterm" name="id4211 38"></a>965 </p></div></div></div></div><div class="sect1" title="Conclusion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id421094"></a>Conclusion</h2></div></div></div><p> 966 <a class="indexterm" name="id421102"></a> 967 <a class="indexterm" name="id421108"></a> 968 <a class="indexterm" name="id421115"></a> 969 <a class="indexterm" name="id421121"></a> 970 <a class="indexterm" name="id421128"></a> 975 971 The Winbind system, through the use of the NSS, PAMs, and appropriate Microsoft RPC calls, have allowed us to 976 972 provide seamless integration of Microsoft Windows NT domain users on a UNIX system. The result is a great 977 973 reduction in the administrative cost of running a mixed UNIX and NT network. 978 </p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id42114 9"></a>Common Errors</h2></div></div></div><p>974 </p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id421140"></a>Common Errors</h2></div></div></div><p> 979 975 Winbind has a number of limitations in its current released version that we hope to overcome in future releases: 980 976 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> … … 990 986 Currently the Winbind PAM module does not take into account possible workstation and logon time 991 987 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" title="NSCD Problem Warning"><div class="titlepage"><div><div><h3 class="title"><a name="id4211 83"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>988 </p></li></ul></div><div class="sect2" title="NSCD Problem Warning"><div class="titlepage"><div><div><h3 class="title"><a name="id421173"></a>NSCD Problem Warning</h3></div></div></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> 993 989 Do not under any circumstances run <code class="literal">nscd</code> on any system 994 990 on which <code class="literal">winbindd</code> is running. … … 997 993 even though NSSWITCH is correctly configured, it will not be possible to resolve 998 994 domain users and groups for file and directory controls. 999 </p></div><div class="sect2" title="Winbind Is Not Resolving Users and Groups"><div class="titlepage"><div><div><h3 class="title"><a name="id4212 17"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p><span class="quote">“<span class="quote">995 </p></div><div class="sect2" title="Winbind Is Not Resolving Users and Groups"><div class="titlepage"><div><div><h3 class="title"><a name="id421207"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p><span class="quote">“<span class="quote"> 1000 996 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 997 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.
Note:
See TracChangeset
for help on using the changeset viewer.
