3219
Comment: urls for the epiphany
|
51
6rZPnq dkg93jfbkSdLk496c
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
This page is for working out the migration of UCC authentication to LDAP. = Current status = Sun LDAP server on manbo set up, DN is `dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au`. [[TableOfContents]] == Configuration Details == Server root is `/var/mps/serverroot`, admin passwords available upon application to [TRS]. `/usr/sbin/directoryserver startconsole` starts the managery console thing. === Referrals to UWA === `dc=uwa,dc=edu,dc=au` goes to `ldap://directory.uwa.edu.au:389/o=The%20University%20of%20Western%20Australia` eg: `ldapsearch -C -x -h manbo -b dc=uwa,dc=edu,dc=au '(cn=Alex Dawson)'` = To Do = * initialize OU entries * load user data from nis and samba * New user creation script, run on manbo?, can use either: * [http://cpu.sourceforge.net/ cpu] and smbpasswd * smbldap-tools. * SSL - our own CA or pay for a cert? * Replication? * Bonus crack - user address book, see (minimally functional) demo at http://mussel.ucc.asn.au/contagged-0.5 * Enable LPK on sshds. = User objectClasses = * Structural *inetOrgPerson * Auxiliary * sambaSamAccount * shadowAccount === Attribute Abuse === Stick dovecot mail_location in preferredDeliveryMethod = Client configuration = * libnss-ldap * nss_base_passwd `ou=People,dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au` (should be the default) * and for hosts with samba: nss_base_passwd `ou=Computers,dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au` * libpam-ldap morwong will only accept {crypt} passwords. Maybe make ignore this and just make morwong ssh-key only? == Solaris LDAP clients == Arrgh the documentation is not very clear about what's going on until you already understand it, particularly if you come from an OpenLDAP backgroud. Basically, instead of binding as the user to the server, the client somehow magically binds with a proxy agent (which doesn't need read access to the user's password mind) and then authenticates the user. So binding as anonymous won't work, since anonymous can't actually bind to the server in a fashion that allows later authentication. Fortunately idsconfig will create the proxy user for you, but you have to understand that you want one first. The exception is if you have SASL/GSSAPI set up, but I think that means you're running kerberos, which we're not. So, to set up a solaris client, run `ldapclient -v init -a proxyDN=cn=proxyagent,ou=profile,dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au 130.95.13.7`, edit `/etc/nsswitch.conf` and replace the `hosts:` entry with `files dns`, then add in `pam_ldap.so.1` to `/etc/pam.conf` as detailed [http://www.opensolaris.org/jive/thread.jspa?threadID=23434 here] or in `pam_ldap(4)`. For googlejuice - this may show itself as the error `pam_ldap: no legal authentication method configured` = Useful URLs = http://lists.samba.org/archive/samba/2005-March/101579.html [[BR]] http://www.unav.es/cti/ldap-smb/smb-ldap-3-howto.html [[BR]] http://samba.org/samba/docs/man/Samba-Guide/happy.html [[BR]] http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/passdb.html [[BR]] http://www.nabble.com/anonymous-binding---is-it-needed---t1261737.html [[BR]] http://groups.google.com/group/comp.unix.solaris/msg/10e8a62bad96f288 |
6rZPnq dkg93jfbkSdLk496c ---- CategoryLecturers |