diff options
| author | Kaz Kylheku <kaz@kylheku.com> | 2016-05-08 12:47:08 -0700 |
|---|---|---|
| committer | Kaz Kylheku <kaz@kylheku.com> | 2016-05-08 12:47:08 -0700 |
| commit | d8570d05b9f554b3e9703994bcd4f3c4534d613e (patch) | |
| tree | dccec85c18fcddac243e4b32d7e3faf63fa904f6 | |
| parent | a90c5ea6d0b3dfe3b3d27328f406b3c346b9663a (diff) | |
| download | tamarind-d8570d05b9f554b3e9703994bcd4f3c4534d613e.tar.gz tamarind-d8570d05b9f554b3e9703994bcd4f3c4534d613e.tar.bz2 tamarind-d8570d05b9f554b3e9703994bcd4f3c4534d613e.zip | |
Fix text which asserts that authentication is SASL.
| -rw-r--r-- | README | 9 |
1 files changed, 7 insertions, 2 deletions
@@ -56,8 +56,9 @@ Tamarind is a CGI program written in the TXR language, running under the Apache web server. Each web request from a web browser launches a new instance of the Tamarind program. -Tamarind authenticates users via SASL---it opens a Unix domain socket -to the saslauthd daemon to validate their user ID and password. +Tamarind authenticates users in one of two ways: using IMAP (opening +a TCP connection to an IMAP server to verify the user name and password) +or SASL (UNIX domain socket to saslauthd server). User sessions are maintained in per-user persistent files stored on the server in a configurable session directory. A browser cookie is associated with an @@ -103,6 +104,10 @@ Here is a visual representation of the architecture: +----------+ +Note that the authentication part of the block diagram shoes +only SASL authentication; this can be configured to IMAP instead. + + 3. HOW TO INSTALL TAMARIND 3.1 Overview. |