This page is for working out the migration of UCC authentication to LDAP.
This page is no longer accurate and is kept only for historical reasons; UCC has migrated to ActiveDirectory instead
OpenLDAP servers set up on mussel (master) and motsugo (replica) under the DN dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au. All machines are pointing to mussel, most to martello as well.
The original Sun LDAP server on manbo which was used to init the database is still around, but not being used.
OpenLDAP is configured in /etc/ldap/slapd.conf in a near-defeault configuration, with the exception of using smbk5pwd, ppolicy and syncprov overlays. There's no fancy console thing, but there's other tools you can use, like GQ and LBE. Admin password available upon application to [TRS]. Data is stored in /var/lib/ldap, and there's a syncagent for martello and a proxyagent for the suns.
On manbo, the server root is /var/mps/serverroot, /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)' also works on mussel.
- initialize OU entries - done
- load user data from nis and samba - done
- New user creation script, run on manbo?, can use either:
cpu and smbpasswd
initial version in /home/wheel/bin/ucc-adduser.ldap, to be used on mussel.
- test password changing - successful
- SSL - our own CA or pay for a cert? our own, investigate free certs for *.uwa.edu.au
- Replication? between mussel and martello - done
Bonus crack - user address book, see (minimally functional) demo at https://mussel.ucc.asn.au/contagged-0.5
- Enable LPK on sshds.
- Stick dovecot mail_location in preferredDeliveryMethod - done
- Stick coke balance into directory, use RFC 4527 methods to update
All clients are using SSL, with a copy of the UCC CA which is run from mooneye:/etc/ssl/CA.pl. CAs are managed on Solaris and Tru64 using certutil.
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 18.104.22.168, 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 here or in pam_ldap(4). For googlejuice - this may show itself as the error pam_ldap: no legal authentication method configured
If you don't have idsconfig, you can use ldapclient genprofile (the replacement for ldap_gen_profile), but something about OpenLDAP or our directory has changed and profiles don't work (producing the undocumented "DUAProfile received from the server has bad format").
So, ala instructions here, run:
# set up TLS certutil -N -d /var/ldap certutil -A -d /var/ldap -n 'CA Name' -i /path/to/cacert.pem -a -t CT # manual ldapclient init ldapclient manual \ -a credentialLevel=proxy \ -a authenticationMethod=tls:simple \ -a defaultSearchBase=dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au \ -a domainName=ucc.gu.uwa.edu.au \ -a defaultServerList="mussel.ucc.gu.uwa.edu.au motsugo.ucc.gu.uwa.edu.au" \ -a preferredServerList="mussel.ucc.gu.uwa.edu.au motsugo.ucc.gu.uwa.edu.au" \ -a proxyDN=cn=proxyagent,ou=profile,dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au \ -a proxyPassword=SOMEPASSWORD \ -a serviceSearchDescriptor=passwd:ou=People,dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au \ -a serviceSearchDescriptor=group:ou=group,dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au \ -a serviceSearchDescriptor=shadow:ou=People,dc=ucc,dc=gu,dc=uwa,dc=edu,dc=au # fix up nss to use DNS svccfg -s name-service/switch setprop config/host = astring: \"files dns\" svccfg -s name-service/switch:default refresh svcadm restart name-service/cache
This works ok, but I still got the dreaded pam_ldap: no legal authentication method configured message until TLS was configured correctly.
Notes on Sun Directory Server and other LDAP servers
The Sun LDAP server supports several private LDAP control OIDs (22.214.171.124.126.96.36.199.188.8.131.52, 2.16.840.1.1137184.108.40.206 and 2.16.840.1.1137220.127.116.11) for the proxy account to obtain account validity information before attempting authentication. If these controls are available, the proxy account doesn't need read access to userPassword, which is good from a security point of view. Unforunately Sun DS doesn't support the LDAP Password Modifiy Extended Operation (defined as 18.104.22.168.4.1.422.214.171.124 in RFC 3062) which PADL libpam_ldap and samba both use to change unix passwords.
In theory the extensions could be added, but even Sun admits the header files is all documentation there is. At least opensolaris being free software lets us read the client source to understand why it's not working. Plus the RFC-track password policy seems to do all the private controls do and more. Further testing indicates it actually does work, and ssh keys can be made to work by just skipping libpam_ldap.so in /etc/pam.conf with a specific sshd-keygen account sections.
So what about Fedora DS? Being a fork of iPlanet, it's very similar to SunDS, including being just as painful as Sun DS to install under Linux, so no real gain there. Plus, it's being converted to FHS at the moment, so we'd just have to reinstall anyway. The documentation is also a little lackluster. Finally, it doesn't support 126.96.36.199.188.8.131.52.184.108.40.206 (which was only added to SunDS recently so ssh keys wouldn't work with libpam_ldap.so, not that that's actually a problem.
Adding linux machines to the samba domain
This isn't really the spot for this, but I didn't think it warranted a completely new page -- BobAdamson
1 11:45 <@Zanchey> who was trying to get motsugo on the domain 2 11:46 <+tpg> Zanchey: bob 3 11:47 <@Zanchey> okay, step one, leave ou=computers the fuck alone 4 11:55 <@Zanchey> step two, run `net rpc join -U zanchey` or whatever 5 11:56 <@Zanchey> step three, run `net rpc testjoin` and profit 6 11:56 <@Zanchey> you may wish to consult the convenient samba documentation where this procedure is laid out 7 11:56 <@Zanchey> http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.html#domain-member-server
Solaris offers a nis server syncing from LDAP
LDAP for Rocket Scientists, easily the most comprehensive of the readable LDAP guides Python LDAP guide Apache Directory Studio, the only worthwhile GUI client