Mercurial > p > roundup > code

changeset 4891:ad3d628e73f2

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 29bc5484969a
files doc/admin_guide.txt doc/customizing.txt
diffstat 2 files changed, 5 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/doc/admin_guide.txt	Tue Apr 15 15:07:30 2014 +0300
+++ b/doc/admin_guide.txt	Tue Apr 15 15:50:33 2014 +0300
@@ -138,8 +138,9 @@
 password and email address for the user. Roundup *must* have its own user
 listing, in order to maintain internal consistency of its data. It is a
 relatively simple exercise to update this listing on a regular basis, or on
-demand, so that it matches an external listing (eg. unix passwd file, LDAP,
-etc.)
+demand, so that it matches an external listing (eg. 
+:ref:`unix passwd file<external-authentication>`,
+`LDAP <http://www.roundup-tracker.org/cgi-bin/moin.cgi/LDAPLogin>`_, etc.)
 
 Roundup identifies users in a number of ways:
 
--- a/doc/customizing.txt	Tue Apr 15 15:07:30 2014 +0300
+++ b/doc/customizing.txt	Tue Apr 15 15:50:33 2014 +0300
@@ -3780,6 +3780,8 @@
 all with the "User" Role.
 
 
+.. _external-authentication:
+
 Using External User Databases
 -----------------------------
Roundup Issue Tracker: http://roundup-tracker.org/