From 927fae1489d7ebf6f49f94818c1ffbc3cb9f1826 Mon Sep 17 00:00:00 2001
From: Quanah Gibson-Mount <quanah@openldap.org>
Date: Thu, 4 Sep 2008 01:09:01 +0000
Subject: [PATCH] More for ITS#5680

---
 CHANGES                     | 2 +-
 doc/man/man5/slapo-pcache.5 | 7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/CHANGES b/CHANGES
index 2eb1186921..0634e28944 100644
--- a/CHANGES
+++ b/CHANGES
@@ -34,8 +34,8 @@ OpenLDAP 2.4.12 Engineering
 		Fixed ODBC library detection (ITS#5602)
 	Documentation
 		Added slapd-ldap(5), slapd-meta(5) noundeffilter (ITS#5614)
+		Fixed slapd-ldap(5), slapd-meta(5), slapo-pcache(5) schema requirements (ITS#5680)
 		Added slapo-retcode(5) retcode.conf location (ITS#5633)
-		Fixed slapd-ldap(5), slapd-meta(5) schema requirements (ITS#5680)
 		admin24 guide updates (ITS#5616)
 		admin24 octetString fix (ITS#5670)
 
diff --git a/doc/man/man5/slapo-pcache.5 b/doc/man/man5/slapo-pcache.5
index 84e55d2acc..eb2b0f5aa5 100644
--- a/doc/man/man5/slapo-pcache.5
+++ b/doc/man/man5/slapo-pcache.5
@@ -182,6 +182,13 @@ The remote server should expose the
 attribute because the underlying database that actually caches the entries 
 may need it for optimal local processing of the queries.
 
+The proxy server should contain all the schema information required for caching.
+Significantly, it needs the schema of attributes used in the query templates.
+If the objectClass attribute is used in a query template, it needs the definition
+of the objectClasses of the entries it is supposed to cache.
+It is the responsibility of the proxy administrator to keep the proxy schema
+lined up with that of the proxied server.
+
 Another potential (and subtle) inconsistency may occur when data is retrieved 
 with different identities and specific per-identity access control
 is enforced by the remote server.
-- 
GitLab