Mercurial > p > roundup > code
comparison doc/admin_guide.txt @ 4891:ad3d628e73f2
docs: Link custom authentication examples in admin guide
| author | anatoly techtonik <techtonik@gmail.com> |
|---|---|
| date | Tue, 15 Apr 2014 15:50:33 +0300 |
| parents | 609edf9de0a5 |
| children | 96dc9f07340a |
comparison
equal
deleted
inserted
replaced
| 4890:609edf9de0a5 | 4891:ad3d628e73f2 |
|---|---|
| 136 | 136 |
| 137 Roundup holds its own user database which primarily contains a username, | 137 Roundup holds its own user database which primarily contains a username, |
| 138 password and email address for the user. Roundup *must* have its own user | 138 password and email address for the user. Roundup *must* have its own user |
| 139 listing, in order to maintain internal consistency of its data. It is a | 139 listing, in order to maintain internal consistency of its data. It is a |
| 140 relatively simple exercise to update this listing on a regular basis, or on | 140 relatively simple exercise to update this listing on a regular basis, or on |
| 141 demand, so that it matches an external listing (eg. unix passwd file, LDAP, | 141 demand, so that it matches an external listing (eg. |
| 142 etc.) | 142 :ref:`unix passwd file<external-authentication>`, |
| 143 `LDAP <http://www.roundup-tracker.org/cgi-bin/moin.cgi/LDAPLogin>`_, etc.) | |
| 143 | 144 |
| 144 Roundup identifies users in a number of ways: | 145 Roundup identifies users in a number of ways: |
| 145 | 146 |
| 146 1. Through the web, users may be identified by either HTTP Basic | 147 1. Through the web, users may be identified by either HTTP Basic |
| 147 Authentication or cookie authentication. If you are running the web | 148 Authentication or cookie authentication. If you are running the web |