Index: openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html,v diff -u -r1.1 -r1.2 --- openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html 8 Oct 2003 10:08:12 -0000 1.1 +++ openacs-4/packages/acs-authentication/www/doc/ext-auth-pam-install.html 14 Oct 2003 09:54:26 -0000 1.2 @@ -1,4 +1,4 @@ -Installing PAM support

Installing PAM support

OpenACS supports PAM authetication via the ns_pam module in AOLserver.

  1. Add PAM support to AOLserver.�OpenACS supports PAM support via the PAM AOLserver +Installing PAM support

    Installing PAM support

    OpenACS supports PAM authetication via the ns_pam module in AOLserver.

    1. 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 @@ -34,7 +34,7 @@ which intermediate programs will be used to check permissions. You may need to install software to perform new types of authentication. -

      • RADIUS in PAM.�

        1. Untar the pam_radius +

          • RADIUS in PAM.�

            1. Untar the pam_radius tarball and compile and install. (more information)

              [root@yourserver root]# cd /usr/local/src/
               [root@yourserver src]# tar xf /tmp/pam_radius-1.3.16.tar
              @@ -58,4 +58,25 @@
                       The OpenACS server itself is the "Local Authority," used by
                       default.

              1. Browse to the authentication administration page, http://yourserver/acs-admin/auth/. - Create and name an authority (in the sitewide admin UI)

              2. Set Authentication to PAM.

              3. If the PAM module contains a password command, you can set Password Management to PAM. If not, the PAM module cannot change the user's password and you should leave this option Disabled.

              4. Leave Account Registration disabed.

              5. Set Batch sync enabled to Yes. Set GetDocumentImplementation to HTTP GET. Set ProcessDocumentImplementation 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.

              6. Click OK.

              7. On the next page, click Configure on the GetDocument Implementation line.

              8. Enter the IncrementalURL and SnapshotURL. These are the URLs which the external Authority will supply with XML files in IMS Enterprise 1.1 format.

              9. Configure your Authority (RADIUS server, etc) to supply XML files to the URLs IncrementalURL and SnapshotURL

          View comments on this page at openacs.org
          + Create and name an authority (in the sitewide admin UI)

        2. Set Authentication to PAM.

        3. If the PAM module contains a password command, you can set Password Management to PAM. If not, the PAM module cannot change the user's password and you should leave this option Disabled.

        4. Leave Account Registration disabed.

        5. Set Batch sync enabled to Yes. Set GetDocumentImplementation to HTTP GET. Set ProcessDocumentImplementation 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.

        6. Click OK.

        7. On the next page, click Configure on the GetDocument Implementation line.

        8. Enter the IncrementalURL and SnapshotURL. These are the URLs which the external Authority will supply with XML files in IMS Enterprise 1.1 format.

        9. Configure your Authority (RADIUS server, etc) to supply XML files to the URLs IncrementalURL and SnapshotURL

          +<enterprise>
          +  <person recstatus = "1">  added person
          +    <sourcedid>
          +      <id>[username]</id>
          +    </sourcedid>
          +    <name>
          +      <family>[last_name]</family>
          +      <given>[first_names]</given>
          +    </name>
          +    <email>[email]</email>
          +    <url>[homepage_url]</url>
          +  </person>
          +  <person recstatus = "2">    modified person
          +    ...
          +  </person>
          +  <person recstatus = "3">    deleted person
          +    <sourcedid>
          +      <id>LL1</id>      only requires username
          +    </sourcedid>
          +  </person>
          +</enterprise>

          (More information: Section�, “IMS Sync driver design”, The IMS 1.1 spec)

    View comments on this page at openacs.org