From 9f87bada9a1f71280122072db1681f68eff892d6 Mon Sep 17 00:00:00 2001
From: Sebastian Hammer <quinn@indexdata.com>
Date: Wed, 11 Apr 2007 02:29:32 +0000
Subject: [PATCH] Added description of session-specific overrides

---
 doc/pazpar2_conf.xml |   18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/doc/pazpar2_conf.xml b/doc/pazpar2_conf.xml
index 3785042..08b4769 100644
--- a/doc/pazpar2_conf.xml
+++ b/doc/pazpar2_conf.xml
@@ -8,7 +8,7 @@
      <!ENTITY % common SYSTEM "common/common.ent">
      %common;
 ]>
-<!-- $Id: pazpar2_conf.xml,v 1.18 2007-04-11 02:23:21 quinn Exp $ -->
+<!-- $Id: pazpar2_conf.xml,v 1.19 2007-04-11 02:29:32 quinn Exp $ -->
 <refentry id="pazpar2_conf">
  <refentryinfo>
   <productname>Pazpar2</productname>
@@ -274,7 +274,7 @@
    </para>
  </refsect1> 
 
- <refsect1><title>TARGET SETTINGS</title>
+ <refsect1 id="target_settings"><title>TARGET SETTINGS</title>
    <para>
      Pazpar2 features a cunning scheme by which you can associate various
      kinds of attributes, or settings with search targets. This is done
@@ -295,6 +295,20 @@
      process any settings files found therein.
    </para>
 
+   <para>
+     Clients of the pazpar2 webservice interface can selectively override
+     settings for individual targets within the scope of one session. This
+     can be used in conjunction with an external authentication system to
+     determine which resources are to be accessible to which users. Pazpar2
+     itself has no notion of end-users, and so can be used in conjunction
+     with any type of authentication system. Similarly, the authentication
+     tokens submitted to access-controlled search targets can similarly be
+     overriden, to allow use of pazpar2 in a consortial or multi-library
+     environment, where different end-users may need to be represented to
+     some search targets in different ways. This, again, can be managed
+     using an external database or other lookup mechanism.
+    </para>
+
    <refsect2><title>SETTINGS FILE FORMAT</title>
      <para>
        Each file contains a root element named &lt;settings&gt;. It may
-- 
1.7.10.4