Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml,v
diff -u -N -r1.28 -r1.29
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 4 Jun 2006 00:45:37 -0000 1.28
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 17 Jul 2006 05:38:37 -0000 1.29
@@ -1,6 +1,6 @@
-
%myvars;
]>
@@ -714,7 +714,7 @@
OpenFTS and tsearch1 use is deprecated in favor of
Tsearch2. See
- Tsearch2. Tsearch2 is much easier to install, requiring only
+ . Tsearch2 is much easier to install, requiring only
compilation of one module from PostgreSQL contrib, with an
automated install process using the tsearch2-driver package.
@@ -1147,9 +1147,9 @@
This section is work in progress. It will detail how you can install Squirrelmail as a webmail frontend for OpenACS, thereby neglecting the need to have a seperate webmail package within OpenACS
[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]# cd www
-[$OPENACS_SERVICE_NAME www]# wget http://cesnet.dl.sourceforge.net/sourceforge/squirrelmail/squirrelmail-1.4.2.tar.gz
-[$OPENACS_SERVICE_NAME www]# tar xfz squirrelmail-1.4.2.tar.gz
-[$OPENACS_SERVICE_NAME www]# mv squirrelmail-1.4.2 mail
+[$OPENACS_SERVICE_NAME www]# wget http://cesnet.dl.sourceforge.net/sourceforge/squirrelmail/squirrelmail-1.4.4.tar.gz
+[$OPENACS_SERVICE_NAME www]# tar xfz squirrelmail-1.4.4.tar.gz
+[$OPENACS_SERVICE_NAME www]# mv squirrelmail-1.4.4 mail
[$OPENACS_SERVICE_NAME www]# cd mail/config
[$OPENACS_SERVICE_NAME www]# ./conf.pl
@@ -1189,12 +1189,22 @@
To enable ns_pam in AOLServer you will first have to edit your config.tcl file and enable the loading of the ns_pam module and configure the aolservers pam configuration file.
- Change config.tcl. Remove the # in front of ns_param nspam ${bindir}/nspam.so to enable the loading of the ns_pam module.
- Change config.tcl. Replace pam_domain in the section ns/server/${server}/module/nspam with aolserver
- Create /etc/pam.d/aolserver.
+
+ Change config.tcl. Remove the
+ # in front of ns_param
+ nspam ${bindir}/nspam.so to enable the loading
+ of the ns_pam module.
+
+
+ Change config.tcl. Replace
+ pam_domain in the section
+ ns/server/${server}/module/nspam
+ with aolserver
+
+ Create /etc/pam.d/aolserver.
[root ns_pam]#cp /var/lib/aolserver/service0/packages/acs-core-docs/www/files/pam-aolserver.txt /etc/pam.d/aolserver
-
+
@@ -1277,17 +1287,19 @@
Configure ns_ldap for traditional use
-
Traditionally OpenACS has supported ns_ldap for authentification by storing the OpenACS password in an encrypted field within the LDAP server called "userPassword". Furthermore a CN field was used for searching for the username, usually userID or something similar. This field is identical to the usernamestored in OpenACS. Therefore the login will only work if you change login method to make use of the username instead.
+
- Change config.tcl. Remove the # in front of ns_param nsldap ${bindir}/nsldap.so to enable the loading of the ns_ldap module.
+
+ Change config.tcl. Remove the # in front of ns_param nsldap ${bindir}/nsldap.so to enable the loading of the ns_ldap module.
+
Configure ns_ldap for use with LDAP bind
-
LDAP authentication usually is done by trying to bind (aka. login) a user with the LDAP server. The password of the user is not stored in any field of the LDAP server, but kept internally. The latest version of ns_ldap supports this method with the ns_ldap bind command. All you have to do to enable this is to configure auth_ldap to make use of the BIND authentification instead. Alternatively you can write a small script on how to calculate the username out of the given input (e.g. if the OpenACS username is malte.fb03.tu, the LDAP request can be translated into "ou=malte,ou=fb03,o=tu" (this example is encoded in auth_ldap and you just have to comment it out to make use of it).
+