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.1.2.20 -r1.1.2.21 --- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp 17 Jun 2017 08:29:27 -0000 1.1.2.20 +++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp 17 Jun 2017 10:15:40 -0000 1.1.2.21 @@ -12,7 +12,7 @@ External Authentication Requirements

-Vision

People have plenty of usernames and passwords already, we +Vision

People have plenty of usernames and passwords already, we don't want them to have yet another. We want people to be able to log in to OpenACS with the same password they use to log in to any other system.

Besides, administrators have better things to do than create @@ -74,7 +74,7 @@

Requirements

-New API

+New API
@@ -229,8 +229,7 @@
FeatureStatusDescription
New API

Regardless of the login method, the user needs to have a row in the OpenACS users table. This can happen through a batch job, in -real-time, or both in combination. We use the IMS -Enterprise 1.1 specification.

Batch job means that we do a synchronization (import new users, +real-time, or both in combination. We use the IMS Enterprise 1.1 specification.

Batch job means that we do a synchronization (import new users, modify changed, purge deleted) on a regular interval, e.g. every night. You can also decide to have a monthly full synchronization, plus daily incremental ones. That's up to you. The advantage is @@ -646,10 +645,10 @@

References