Index: openacs-4/packages/acs-authentication/www/doc/acs-authentication.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/acs-authentication.html,v diff -u -r1.3.2.1 -r1.3.2.2 --- openacs-4/packages/acs-authentication/www/doc/acs-authentication.html 10 Aug 2019 15:15:49 -0000 1.3.2.1 +++ openacs-4/packages/acs-authentication/www/doc/acs-authentication.html 1 Aug 2024 07:38:16 -0000 1.3.2.2 @@ -48,7 +48,7 @@
Those configurations simply will perform the tcl proc that is defined in the SC above described for the given SC implementation that you choose. In other words:
+Those configurations simply will perform the Tcl proc that is defined in the SC above described for the given SC implementation that you choose. In other words:
Then you can enter your specific values for your server, is likely that the recomemded ones will work fine.
Hint: nssha (SSHA) doesn't work well with LDAP use ns_passwd or another encryption method (MD5...)
-You can make your users to logging using the email or username, by changing the parameter at the kernel named: UseEmailForLoginP under Security section. If username is used for logging, it will ask for the authority to use, since username is unique by authority but not for the entire openacs installation (can exists several identic usernames but each one belongs to a different authority).
+You can make your users to logging using the email or username, by changing the parameter at the kernel named: UseEmailForLoginP under Security section. If username is used for logging, it will ask for the authority to use, since username is unique by authority but not for the entire openacs installation (can exists several identical usernames but each one belongs to a different authority).
acs-authentication defines a set of SC to interact with the different authentication implementations (LDAP or PAM):