Difference between revisions of "LDAP Ramblings"
| Line 27: | Line 27: | ||
====Websites==== | ====Websites==== | ||
| + | *[http://www.openldap.org/doc/admin24/ OpenLDAP Admin Guide] | ||
*[http://www.openldap.org/ OpenLDAP] | *[http://www.openldap.org/ OpenLDAP] | ||
*[http://www.faqs.org/docs/Linux-HOWTO/LDAP-HOWTO.html Linux LDAP Howto] | *[http://www.faqs.org/docs/Linux-HOWTO/LDAP-HOWTO.html Linux LDAP Howto] | ||
*[http://www.linuxjournal.com/article/5505 LinuxJournal - Highly Available LDAP] | *[http://www.linuxjournal.com/article/5505 LinuxJournal - Highly Available LDAP] | ||
*[http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.3/suselinux-adminguide_en/cha.ldap.html SUSE LDAP docs] | *[http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.3/suselinux-adminguide_en/cha.ldap.html SUSE LDAP docs] | ||
Revision as of 07:57, 8 January 2008
Intro
On the IAC's user accessable Linux servers (Brems, web, Inca, backup) there is a need for centralized user authentication. With the addition of email users this need becomes critical. The proposed solution is to use OpenLDAP replicated across the mail servers for redundancy.
Clients
Linux Clients
Administrative users will retain entries in the local /etc/passwd and /etc/shadow files for troubleshooting access. All other users will exist in LDAP and will have individual server permissions.
Email Clients
Ideally email users can be accommodated without having local accounts. If this is not possible, the local shell can be set to disallow logins for security purposes.
Windows Clients
Currently not planned, but possible once the setup has been proven. This would allow users to log into any machine using their username and login. Only a select few machines (data aquisition etc.) would retain generic iacuser access.
LDAP Schema
basedn = "cn=Auth,dc=iac,dc=isu,dc=edu"
Replication
- Requires ntp time syncronization between replication servers.