http://commons.oreilly.com/wiki/index.php?title=Linux_in_a_Windows_World/Centralized_Authentication_Tools&action=history Revision history for this page on the wiki en MediaWiki 1.11.0 Wed, 22 May 2013 12:15:21 GMT http://commons.oreilly.com/wiki/index.php?title=Linux_in_a_Windows_World/Centralized_Authentication_Tools&diff=9550&oldid=prev <p>Initial conversion from Docbook</p> <table style="background-color: white; color:black;"> <col class='diff-marker' /> <col class='diff-content' /> <col class='diff-marker' /> <col class='diff-content' /> <tr> <td colspan='2' style="background-color: white; color:black;">←Older revision</td> <td colspan='2' style="background-color: white; color:black;">Revision as of 23:06, 11 March 2008</td> </tr> </table> Tue, 11 Mar 2008 23:06:43 GMT Docbook2Wiki http://commons.oreilly.com/wiki/index.php/Talk:Linux_in_a_Windows_World/Centralized_Authentication_Tools http://commons.oreilly.com/wiki/index.php?title=Linux_in_a_Windows_World/Centralized_Authentication_Tools&diff=8772&oldid=prev <p>Initial conversion from Docbook</p> <p><b>New page</b></p><div>{{Linux in a Windows World/TOC}}<br /> Networks with many computers frequently set aside one system as an ''authentication server''—a computer that authenticates users for the benefit of other computers. This practice can greatly simplify account maintenance, because you need to maintain only one set of user accounts rather than separate accounts on each computer. This goal is more complex on a multi-OS network than in a single-OS environment, though, because different OSs support different protocols for performing these tasks. This part of the book looks at three protocols that can be used in a mixed Windows/Linux environment: [[Linux in a Windows World/Centralized Authentication Tools/Using NT Domains for Linux Authentication|Chapter 7]] describes using an NT domain controller, [[Linux in a Windows World/Centralized Authentication Tools/Using LDAP|Chapter 8]] describes using the Lightweight Directory Access Protocol (LDAP), and [[Linux in a Windows World/Centralized Authentication Tools/Kerberos Configuration and Use|Chapter 9]] describes using Kerberos. [[Linux in a Windows World/Centralized Authentication Tools/Using NT Domains for Linux Authentication|Chapter 7]] emphasizes Linux configuration as an authentication client; the Linux server and Windows client sides are covered in [[Linux in a Windows World/Sharing Files and Printers/Managing a NetBIOS Network with Samba|Chapter 5]]. [[Linux in a Windows World/Centralized Authentication Tools/Using LDAP|Chapter 8]] and [[Linux in a Windows World/Centralized Authentication Tools/Kerberos Configuration and Use|Chapter 9]] describe both client and server configuration for Linux and client configuration for Windows.<br /> <br /> Which tool should you use? All can do the job, but each has its strengths and weaknesses. Broadly speaking, using an NT domain controller works well when you have an existing NT domain controller for file share access and want to apply this existing account database to other purposes. LDAP provides the best support for Linux account data and can also work well with Windows 200x/XP systems, but it doesn't support Windows 9x/Me very well. Kerberos was designed to provide a single sign-on—that is, to enable users to enter their passwords once per session, even if they log in and out of multiple servers during this session. It doesn't maintain all the necessary account data, though, and it can be tricky to use for some cross-platform tasks.</div> Tue, 11 Mar 2008 21:46:06 GMT Docbook2Wiki http://commons.oreilly.com/wiki/index.php/Talk:Linux_in_a_Windows_World/Centralized_Authentication_Tools