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 @@
  • Account Registration (where to create new accounts)
  • On-Demand Sync (to get user info from the source in real time)
  • -

    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):

      @@ -111,7 +111,7 @@
      1. The user enters the email/user & password
      2. It will search the user in the users table and return the authority_id
      3. -
      4. With that authority_id it will find the respective SC implementation which contains the adequate tcl proc for the authentication process
      5. +
      6. With that authority_id it will find the respective SC implementation which contains the adequate Tcl proc for the authentication process
      7. That proc will check the identity of the user based on the password (right now could be locally, pam or ldap authenticated, though this model supports N methods of authentication)
    View comments on this page at openacs.org
    Index: openacs-4/packages/acs-messaging/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/www/doc/requirements.html,v diff -u -r1.3.2.1 -r1.3.2.2 --- openacs-4/packages/acs-messaging/www/doc/requirements.html 15 Aug 2019 10:20:04 -0000 1.3.2.1 +++ openacs-4/packages/acs-messaging/www/doc/requirements.html 1 Aug 2024 07:38:16 -0000 1.3.2.2 @@ -58,7 +58,7 @@

    The ACS Messaging package defines a data model and API for the - storage and retrieval of messages. While the package standarizes how + storage and retrieval of messages. While the package standardizes how messages are stored, applications may use any data model they want for higher level organization of messages into threads, forums, and so on. ACS Messaging places no organizational constraints on Index: openacs-4/packages/acs-service-contract/www/doc/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.html,v diff -u -r1.7 -r1.7.2.1 --- openacs-4/packages/acs-service-contract/www/doc/index.html 18 May 2018 07:56:07 -0000 1.7 +++ openacs-4/packages/acs-service-contract/www/doc/index.html 1 Aug 2024 07:38:16 -0000 1.7.2.1 @@ -30,9 +30,9 @@ including both input and outputs as well as metadata such as caching.

  • implementation - an implementation is a set of concrete functions - that fufills an interface.
  • + that fulfillss an interface.
  • implementation alias - is the method of an implementation that - fufills a given operation of the contract.
  • + fulfillss a given operation of the contract.
  • bindings - association between an interface and an implementation.
  • types - define the kind of input and outputs a operation receives.
  • @@ -47,7 +47,7 @@

    with acs contracts.

    Implement the Contract

    FAQ

    Why Does an implementation reference an interface?

    This might seem a little strange since a binding is the official - reference between an implementation and an interface. However + reference between an implementation and an interface. However, it is quite possible that an implementation for interface might exist prior to the interface being defined, ie the interface defining package is not installed. By retaining this information @@ -71,7 +71,7 @@ container for operations. contract_desc is a text description of the contract.