Browse to the authentication administration page, +
Browse to the authentication administration page, http://yourserver/acs-admin/auth/ and choose an authority for batch sync.
Set Batch sync enabled to Yes. Set GetDocument Implementation to HTTP GET. Set ProcessDocument Implementation to IMS Enterprise 1.1. These settings will cause OpenACS to attempt to retrieve via HTTP a list of users in XML format from a location we will specify in a few steps.
Click OK.
On the next page, click Configure on the GetDocument Implementation line.
Enter either or both the IncrementalURL and SnapshotURL. These are the URLs which the external Authority will supply with XML files in IMS Enterprise 1.1 format.
Configure your Authority (RADIUS server, etc) to supply XML files to the URLs IncrementalURL and SnapshotURL. A typical set of incremental file record - looks like:
+ looks like:<?xml version="1.0" encoding="ISO-8859-1"?> <enterprise> - <person recstatus = "1"> added person + <properties> + <datasource>FOO</datasource> + <target>dotLRN</target> + <type>DB Increment</type> + <datetime>28-oct-2003#16:06:02</datetime> + </properties> + <person recstatus = "1"> <sourcedid> - <id>[username]</id> + <source>FOO</source> + <id>karlf</id> </sourcedid> <name> - <family>[last_name]</family> - <given>[first_names]</given> + <n> + <given>Karl</given> + <family>Fritz</family> + <prefix></prefix> + </n> </name> - <email>[email]</email> - <url>[homepage_url]</url> + <email>karlf@example.net</email> </person> - <person recstatus = "2"> modified person + <person recstatus = "2"> <!--modified person--> ... </person> - <person recstatus = "3"> deleted person - <sourcedid> - <id>LL1</id> only requires username - </sourcedid> + <person recstatus = "3"> <!--deleted person--> + <sourcedid> + <id>LL1</id> <!--only requires username--> + </sourcedid> </person> -</enterprise>A snapshot file is similar but doesn't have recstatus, - since it's not a delta but a list of valid records. -
-<enterprise> - <person> - <sourcedid> - <id>[username]</id> - </sourcedid> - <name> - <family>[last_name]</family> - <given>[first_names]</given> - </name> - <email>[email]</email> - <url>[homepage_url]</url> - </person> - ... </enterprise> -(More information: Section�, “IMS Sync driver design”, The IMS 1.1 spec)
A snapshot file is similar but doesn't have recstatus, + since it's not a delta but a list of valid records. See the larger example in the design document for more details. +
(More information: the section called “IMS Sync driver design”, The IMS 1.1 spec)
Table of Contents
...
Installing AOLserver LDAP support.�Forthcoming. (more information)
Install auth-ldap OpenACS service package.�Install auth-ldap and restart the server.
...
Installing AOLserver LDAP support.�Forthcoming. (more information)
Install auth-ldap OpenACS service package.�Install auth-ldap and restart the server.
OpenACS supports PAM authetication via the ns_pam module in AOLserver.
Add PAM support to AOLserver.�OpenACS supports PAM support via the PAM AOLserver +
OpenACS supports PAM authetication via the ns_pam module in AOLserver.
Add PAM support to AOLserver.�OpenACS supports PAM support via the PAM AOLserver module. PAM is system of modular support, and can provide local (unix password), RADIUS, LDAP (more information), and other forms of @@ -22,11 +22,11 @@ gcc -shared -nostartfiles -o nspam.so nspam.o pam_support.o -lpam [root@yourserver nspam]# make install [root@yourserver nspam]# -
cd /usr/local/src/aolserver
+cd /usr/local/src/aolserver
tar xzf /tmp/ns_pam-0.1.tar.gz
cd nspam
make
-make installSet up a PAM domain.�A PAM domain is a set of rules for granting +make install
Set up a PAM domain.�A PAM domain is a set of rules for granting privileges based on other programs. Each instance of AOLserver uses a domain; different aolserver instances can use the same domain but one AOLserver instance @@ -45,11 +45,11 @@ ld -Bshareable pam_radius_auth.o md5.o -lpam -o pam_radius_auth.so [root@yourserver pam_radius-1.3.16]# cp pam_radius_auth.so /lib/security/pam_radius_auth.so [root@yourserver pam_radius-1.3.16]# -
cd /usr/local/src/
+cd /usr/local/src/
tar xf /tmp/pam_radius-1.3.16.tar
cd pam_radius-1.3.16
make
-cp pam_radius_auth.so /lib/security/pam_radius_auth.soDebian users: apt-get install libpam-radius-auth
Set up the PAM domain. Recent PAM +cp pam_radius_auth.so /lib/security/pam_radius_auth.so
Debian users: apt-get install libpam-radius-auth
Set up the PAM domain. Recent PAM distributions have a different file for each domain, all in /etc/pam.d. Previous PAM setups put all domain configuration lines Index: openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html,v diff -u -r1.2 -r1.3 --- openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html 20 Oct 2003 15:44:31 -0000 1.2 +++ openacs-4/packages/acs-authentication/www/doc/ims-sync-driver-design.html 19 Feb 2004 14:59:42 -0000 1.3 @@ -1,12 +1,12 @@ -