Index: openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl,v diff -u -r1.1 -r1.2 --- openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl 14 Nov 2014 18:20:17 -0000 1.1 +++ openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl 28 Mar 2018 17:00:40 -0000 1.2 @@ -2975,7 +2975,7 @@ set index_eq "" if { $p1_arr(index_equation) ne "" } { # validate equation or set empty - # only allow + - / * $, logical comparisions > < == != and numbers. $number converts to one of the available row numbers that returns a number from in p4 + # only allow + - / * $, logical comparisons > < == != and numbers. $number converts to one of the available row numbers that returns a number from in p4 regsub -nocase -all -- {[^\$\/\+\-\*\(\)\.\<\>\=\!\ 0-9]+} $p1_arr(index_equation) "" index_eq # add extra spaces to help expr avoid misinterpretations, but can't assume that for negative numbers vs. minus sign regsub -nocase -all -- {([\/\+\*\(\)])} $index_eq " \1 " index_eq @@ -3494,7 +3494,7 @@ # For strict critical path, create a list of lists, where # each list is a list of activity and dependencies from start to finish (aka path). - # The longest duration path is the strict defintion of critical path. + # The longest duration path is the strict definition of critical path. # create dependency check equations ns_log Notice "acc_fin::scenario_prettify.1797: scenario '$scenario_tid' create equations for checking if dependencies are met." Index: openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp,v diff -u -r1.3 -r1.4 --- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp 8 Nov 2017 09:42:10 -0000 1.3 +++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp 28 Mar 2018 17:00:40 -0000 1.4 @@ -49,7 +49,7 @@ effect between usability and security, because when authentication schemes have poor usability, users will think up ways to circumvent them.
Open and modular: The design should be on the one hand open to -add other authentification mechanisms when needed and on the other +add other authentication mechanisms when needed and on the other hand very modular to enable a start with minimal requirements (driver implementations) as soon as possible.
The problem can be split into several logically separate parts. @@ -803,4 +803,4 @@ Chapter 16. Releasing OpenACS" homeLink="index" homeLabel="Home" upLink="kernel-doc" upLabel="Up"> - \ No newline at end of file + Index: openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html,v diff -u -r1.42 -r1.43 --- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html 8 Nov 2017 09:42:10 -0000 1.42 +++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html 28 Mar 2018 17:00:40 -0000 1.43 @@ -41,7 +41,7 @@ effect between usability and security, because when authentication schemes have poor usability, users will think up ways to circumvent them.
Open and modular: The design should be on the one hand - open to add other authentification mechanisms when needed and on + open to add other authentication mechanisms when needed and on the other hand very modular to enable a start with minimal requirements (driver implementations) as soon as possible.
Configure ns_ldap for traditional use. Traditionally OpenACS has supported -ns_ldap for authentification by storing the OpenACS password in an +ns_ldap for authentication 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. @@ -77,7 +77,7 @@ 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. +auth_ldap to make use of the BIND authentication 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 @@ -93,4 +93,4 @@ rightLink="aolserver" rightLabel="Next" rightTitle="Install AOLserver 3.3oacs1" homeLink="index" homeLabel="Home" upLink="install-more-software" upLabel="Up"> - \ No newline at end of file + Index: openacs-4/packages/acs-core-docs/www/install-ldap-radius.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-ldap-radius.html,v diff -u -r1.12 -r1.13 --- openacs-4/packages/acs-core-docs/www/install-ldap-radius.html 8 Nov 2017 09:42:10 -0000 1.12 +++ openacs-4/packages/acs-core-docs/www/install-ldap-radius.html 28 Mar 2018 17:00:40 -0000 1.13 @@ -47,15 +47,15 @@
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. + Traditionally OpenACS has supported ns_ldap for authentication 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.
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). + 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 authentication 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).