Changes

If your software is just meant for a small group of people, maybe the administrator model will work for you. However, if you want to make your service all-Williams and Williams-only, you'll want to authenticate against LDAP servers, the same thing [http://blackboard.williams.edu Blackboard] uses to check your password. See if your package either has LDAP support built in or if it's available as an extension or plugin. You might want to check the software maintainer's site for such an extension.

Here are settings for authenticating different types of users. Ideally, you can authenticate more than one type, but that will depend what kind of support your software has. Of course, if you are a true See [[Students with Computer Skills|badassLDAP]], you shouldn't be afraid to write your own extension to handle multiple LDAP settings. In all cases, you need to somehow substitute $USER with the name of the user that's logging in. ===Williams Students===  Server: nds2.williams.edu (or nds1.williams.edu) Bind domain: cn=$USER,ou=student,o=williams SSL: no ===WSO accounts=== These include some students and some alumni.  Server: ursula Bind domain: uid=$USER,cn=users,dc=williams,dc=edu SSL: yes ===Williams Faculty===  Server: nds2.williams.edu Bind domain: cn=$USER,ou=faculty,o=williams SSL: no ===Williams Staff===  Server: nds2.williamsfor more information.edu Bind domain: cn=$USER,ou=staff,o=williams SSL: no