Index: openacs-4/packages/acs-admin/www/apm/version-upgrade.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-admin/www/apm/version-upgrade.tcl,v diff -u -N -r1.3 -r1.4 --- openacs-4/packages/acs-admin/www/apm/version-upgrade.tcl 7 Aug 2017 23:47:45 -0000 1.3 +++ openacs-4/packages/acs-admin/www/apm/version-upgrade.tcl 11 Jul 2018 21:57:26 -0000 1.4 @@ -17,7 +17,7 @@ [list "version-view?version_id=$version_id" "$pretty_name $version_name"] \ $title] -# Disable all previous versions of this packae. +# Disable all previous versions of this package. apm_version_upgrade $version_id # Instruct user to run SQL upgrade scripts. Index: openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.adp,v diff -u -N -r1.4 -r1.5 --- openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.adp 30 Apr 2018 08:12:47 -0000 1.4 +++ openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.adp 11 Jul 2018 21:57:26 -0000 1.5 @@ -21,7 +21,7 @@ your OpenACS instance using the password they are accustomed to using for other things at your institution.

Background. The original OpenACS LDAP -implementation (which has been depreciated by this package) treated +implementation (which has been deprecated by this package) treated the LDAP server as another data store similar to Oracle or Postgresql. It opened a connection using a privileged account and read or stored an encrypted password for the user in question. This @@ -150,4 +150,4 @@ rightLink="configure-batch-sync" rightLabel="Next" rightTitle="Configure Batch Synchronization" homeLink="index" homeLabel="Home" upLink="ext-auth-install" upLabel="Up"> - \ No newline at end of file + Index: openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.html,v diff -u -N -r1.6 -r1.7 --- openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.html 7 Aug 2017 23:47:46 -0000 1.6 +++ openacs-4/packages/acs-authentication/www/doc/ext-auth-ldap-install.html 11 Jul 2018 21:57:26 -0000 1.7 @@ -1,7 +1,7 @@ Using LDAP/Active Directory with OpenACS

Alex logo
Prev Installation Next

Using LDAP/Active Directory with OpenACS

by John Sequeira, Michael Steigman, and Carl Blesius. OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

ToDo: Add/verify information on on-demand sync, account registration, and batch synchronization. Add section on ldapsearch.

Overview. You do not want to make users remember yet another password and username. If you can avoid it you do not want to store their passwords either. This document should help you set your system up so your users can seamlessly log in to your OpenACS instance using the password they are accustomed to using for other things at your institution.

Background. The original OpenACS LDAP implementation (which has been depreciated by this package) treated the LDAP server as another data store similar to Oracle or Postgresql. It opened a connection using a privileged account and read or stored an encrypted password for the user in question. This password was independent of the user's operating system or network account, and had to be synchronized if you wanted the same password for OpenACS.Save their passwords? Sync passwords? Deal with forgotten password requests? No Thanks. Using ldap bind, you can delegate authentication completely to LDAP. This way you can let the IT department (if you are lucky) worry about password storage/synchronization/etc. The bind operation takes a username and password and returns a true of false depending on whether they match up. This document takes the 'bind' approach so that your users LDAP/AD password (or whatever else you use) can be used to login to OpenACS.

Note on Account Creation. On the authentication driver configure screens, you will also see lots of options for synchronizing users between your directory and OpenACS. This document takes the approach of provisioning users on demand instead of ahead-of-time. This means that when they attempt to login to OpenACS, if they have a valid Windows account, we'll create an account for them in OpenACS and log them in.

  1. Installing AOLserver LDAP support (openldap and nsldap). Install openldap and nsldap using +

ToDo: Add/verify information on on-demand sync, account registration, and batch synchronization. Add section on ldapsearch.

Overview. You do not want to make users remember yet another password and username. If you can avoid it you do not want to store their passwords either. This document should help you set your system up so your users can seamlessly log in to your OpenACS instance using the password they are accustomed to using for other things at your institution.

Background. The original OpenACS LDAP implementation (which has been deprecated by this package) treated the LDAP server as another data store similar to Oracle or Postgresql. It opened a connection using a privileged account and read or stored an encrypted password for the user in question. This password was independent of the user's operating system or network account, and had to be synchronized if you wanted the same password for OpenACS.Save their passwords? Sync passwords? Deal with forgotten password requests? No Thanks. Using ldap bind, you can delegate authentication completely to LDAP. This way you can let the IT department (if you are lucky) worry about password storage/synchronization/etc. The bind operation takes a username and password and returns a true of false depending on whether they match up. This document takes the 'bind' approach so that your users LDAP/AD password (or whatever else you use) can be used to login to OpenACS.

Note on Account Creation. On the authentication driver configure screens, you will also see lots of options for synchronizing users between your directory and OpenACS. This document takes the approach of provisioning users on demand instead of ahead-of-time. This means that when they attempt to login to OpenACS, if they have a valid Windows account, we'll create an account for them in OpenACS and log them in.

  1. Installing AOLserver LDAP support (openldap and nsldap). Install openldap and nsldap using the document Malte created Next, modify your config.tcl file as directed in the nsldap README. Here's what the relevant additions should look like:

       
 # LDAP authentication
Index: openacs-4/packages/acs-tcl/tcl/community-core-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-tcl/tcl/community-core-procs.tcl,v
diff -u -N -r1.96 -r1.97
--- openacs-4/packages/acs-tcl/tcl/community-core-procs.tcl	7 Jul 2018 07:48:44 -0000	1.96
+++ openacs-4/packages/acs-tcl/tcl/community-core-procs.tcl	11 Jul 2018 21:57:26 -0000	1.97
@@ -427,7 +427,7 @@
     @param authority_id if user_id was not specified, but a username
                         was given, this proc will try to retrieve a
                         user_id from username and authority. If
-                        authority_id is lect blank, will default to
+                        authority_id is left blank, will default to
                         the local authority.
     @param username if specified and no user_id was give, will be used
                     to retrieve user_id from the authority. If no
Index: openacs-4/packages/acs-tcl/tcl/defs-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-tcl/tcl/defs-procs.tcl,v
diff -u -N -r1.74 -r1.75
--- openacs-4/packages/acs-tcl/tcl/defs-procs.tcl	28 May 2018 18:10:17 -0000	1.74
+++ openacs-4/packages/acs-tcl/tcl/defs-procs.tcl	11 Jul 2018 21:57:26 -0000	1.75
@@ -591,7 +591,7 @@
     {-message_2 ""}
     {-template "/packages/acs-tcl/lib/progress-bar"}
 } {
-    Return a proress bar.
+    Return a progress bar.
 
     
    Example:
 
Index: openacs-4/packages/acs-templating/www/scripts/xinha/attach-file.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/scripts/xinha/attach-file.tcl,v
diff -u -N -r1.22 -r1.23
--- openacs-4/packages/acs-templating/www/scripts/xinha/attach-file.tcl	18 Jun 2018 07:28:49 -0000	1.22
+++ openacs-4/packages/acs-templating/www/scripts/xinha/attach-file.tcl	11 Jul 2018 21:57:26 -0000	1.23
@@ -35,7 +35,7 @@
 }
 
 if {!$write_p} {
-    # if parent_id does not exist yet, let's use the pacakage_id
+    # if parent_id does not exist yet, let's use the package_id
     if { ![db_0or1row check_parent {select object_id from acs_objects where object_id = :parent_id}] } {
         set parent_id $package_id
     }
Index: openacs-4/packages/acs-templating/www/scripts/xinha/attach-image.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/scripts/xinha/attach-image.tcl,v
diff -u -N -r1.15 -r1.16
--- openacs-4/packages/acs-templating/www/scripts/xinha/attach-image.tcl	1 May 2018 09:34:09 -0000	1.15
+++ openacs-4/packages/acs-templating/www/scripts/xinha/attach-image.tcl	11 Jul 2018 21:57:26 -0000	1.16
@@ -31,7 +31,7 @@
 }
 
 if {!$write_p} {
-    # if parent_id does not exist yet, let's use the pacakage_id
+    # if parent_id does not exist yet, let's use the package_id
     if { ![db_0or1row check_parent {select object_id from acs_objects where object_id = :parent_id}] } {
         set parent_id $package_id
     }
Index: openacs-4/packages/dotlrn/www/doc/nomenclature.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn/www/doc/nomenclature.adp,v
diff -u -N -r1.4 -r1.5
--- openacs-4/packages/dotlrn/www/doc/nomenclature.adp	7 Aug 2017 23:48:09 -0000	1.4
+++ openacs-4/packages/dotlrn/www/doc/nomenclature.adp	11 Jul 2018 21:57:26 -0000	1.5
@@ -71,7 +71,7 @@
 
 
    
 
-A communty with closed join policy is not visible to
+A community with closed join policy is not visible to
 non-members. Users become members only when explicitly added by the
 community administrator.
 
Index: openacs-4/packages/dotlrn-portlet/sql/oracle/dotlrn-members-staff-portlet-create.sql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn-portlet/sql/oracle/dotlrn-members-staff-portlet-create.sql,v
diff -u -N -r1.6 -r1.7
--- openacs-4/packages/dotlrn-portlet/sql/oracle/dotlrn-members-staff-portlet-create.sql	30 Sep 2003 13:11:40 -0000	1.6
+++ openacs-4/packages/dotlrn-portlet/sql/oracle/dotlrn-members-staff-portlet-create.sql	11 Jul 2018 21:57:26 -0000	1.7
@@ -16,7 +16,7 @@
 
 --
 
--- Creates dotlrn datasource for showing staff members for a comunity
+-- Creates dotlrn datasource for showing staff members for a community
 
 -- Copyright (C) 2001 MIT
 -- @author Arjun Sanyal (arjun@openforce.net)
Index: openacs-4/packages/dotlrn-portlet/sql/postgresql/dotlrn-members-staff-portlet-create.sql
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn-portlet/sql/postgresql/dotlrn-members-staff-portlet-create.sql,v
diff -u -N -r1.4 -r1.5
--- openacs-4/packages/dotlrn-portlet/sql/postgresql/dotlrn-members-staff-portlet-create.sql	27 Oct 2014 16:41:22 -0000	1.4
+++ openacs-4/packages/dotlrn-portlet/sql/postgresql/dotlrn-members-staff-portlet-create.sql	11 Jul 2018 21:57:26 -0000	1.5
@@ -16,7 +16,7 @@
 
 --
 
--- Creates dotlrn datasource for showing staff members for a comunity
+-- Creates dotlrn datasource for showing staff members for a community
 
 -- Copyright (C) 2001 MIT
 -- @author Arjun Sanyal (arjun@openforce.net)
Index: openacs-4/packages/static-pages/www/doc/static-pages-requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/static-pages/www/doc/static-pages-requirements.html,v
diff -u -N -r1.1 -r1.2
--- openacs-4/packages/static-pages/www/doc/static-pages-requirements.html	20 Apr 2001 20:51:23 -0000	1.1
+++ openacs-4/packages/static-pages/www/doc/static-pages-requirements.html	11 Jul 2018 21:57:26 -0000	1.2
@@ -306,7 +306,7 @@
 >2.2.5.2. Admin UI: commentability designation
    
	For any given static page, the administator will be able to 
+>
	For any given static page, the administrator will be able to 
 	specify the following:
    \ No newline at end of file +> Index: openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl,v diff -u -N -r1.136 -r1.137 --- openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl 9 Jul 2018 08:12:21 -0000 1.136 +++ openacs-4/packages/xotcl-core/tcl/05-db-procs.tcl 11 Jul 2018 21:57:26 -0000 1.137 @@ -532,7 +532,7 @@ } proc ::xo::db::pg_0or1row {sql} { - ns_log notice "::xo::db::pg_0or1row decprecated" + ns_log notice "::xo::db::pg_0or1row deprecated" ::db_with_handle h { return [uplevel [list ns_pg_bind 0or1row $h {*}$bindOpt $sql]] }