<br><br><div class="gmail_quote">On 5 September 2011 10:10, Laurence Southon <span dir="ltr"><<a href="mailto:laurence@southon.uk.net">laurence@southon.uk.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 05/09/11 08:24, Peter Childs wrote:<br>
> Any ideas, I can't think of anything that fits the bill.<br>
<br>
</div>LDAP?<br>
<br>
See the bottom of this page:<br>
<br>
<a href="http://wiki.debian.org/LDAP/PAM" target="_blank">http://wiki.debian.org/LDAP/PAM</a><br>
<br>
for how to store locally for when the server not available, though the<br>
other approach would be to have two LDAP servers and replicate.<br>
<br>
Not easy to implement, but a useful howto here:<br>
<br>
<a href="http://techpubs.spinlocksolutions.com/dklar/ldap.html" target="_blank">http://techpubs.spinlocksolutions.com/dklar/ldap.html</a><br>
<br>
HTH,<br>
<br>
LS<br>
--<br>
Laurence Southon<br>
Tiger Computing, Bexley<br>
<a href="http://www.tiger-computing.co.uk" target="_blank">www.tiger-computing.co.uk</a><br>
<br>
_______________________________________________<br>
Kent mailing list<br>
<a href="mailto:Kent@mailman.lug.org.uk">Kent@mailman.lug.org.uk</a><br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/kent" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/kent</a><br>
</blockquote></div><br><div>Hmm quick lesson on LDAP docs.</div><div><br></div><div>Its more complicated than that.</div><div><br></div><div>LDAP is just a database, its a pain, badly documented etc etc etc (short answer I hate it but that might be a personal view)</div>
<div><br></div><div>most LDAP based setups store there passwords in Kerberos and only the user information (such as shell, name, and home directory stuff) actually in LDAP although Kerberos can store its data in LDAP, which creates an interesting loop. </div>
<div><br></div><div>Anyway it still fails when the network fails, or you password server is down for what ever reason, true you can have Salves or a distributed database but its not that easy under linux.</div><div><br></div>
<div>My current idea is to use Kerberos, but that still does not solve the user information stuff, </div><div><br></div><div><br></div><div><br></div><div>Peter.</div>