Mercurial > p > roundup > code
comparison doc/admin_guide.txt @ 6265:b2eb59ada444
Replace http:....roundup-tracker.org with https. Also fix wiki links.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 09 Sep 2020 21:27:55 -0400 |
| parents | 5105df69145d |
| children | a635a60ffb84 |
comparison
equal
deleted
inserted
replaced
| 6264:48fa77813563 | 6265:b2eb59ada444 |
|---|---|
| 198 password and email address for the user. Roundup *must* have its own user | 198 password and email address for the user. Roundup *must* have its own user |
| 199 listing, in order to maintain internal consistency of its data. It is a | 199 listing, in order to maintain internal consistency of its data. It is a |
| 200 relatively simple exercise to update this listing on a regular basis, or on | 200 relatively simple exercise to update this listing on a regular basis, or on |
| 201 demand, so that it matches an external listing (eg. | 201 demand, so that it matches an external listing (eg. |
| 202 :ref:`unix passwd file<external-authentication>`, | 202 :ref:`unix passwd file<external-authentication>`, |
| 203 `LDAP <http://www.roundup-tracker.org/cgi-bin/moin.cgi/LDAPLogin>`_, etc.) | 203 `LDAP <https://wiki.roundup-tracker.org/LDAPLogin>`_, etc.) |
| 204 | 204 |
| 205 Roundup identifies users in a number of ways: | 205 Roundup identifies users in a number of ways: |
| 206 | 206 |
| 207 1. Through the web, users may be identified by either HTTP Basic | 207 1. Through the web, users may be identified by either HTTP Basic |
| 208 Authentication or cookie authentication. If you are running the web | 208 Authentication or cookie authentication. If you are running the web |