From 29486000b2391364c8b3275bfa0ae632b81c2ea8 Mon Sep 17 00:00:00 2001
From: Russ Allbery <rra@stanford.edu>
Date: Wed, 25 Mar 2009 03:47:42 +0000
Subject: Add the shibboleth.xml object naming convention.

---
 docs/stanford-naming | 8 ++++++++
 1 file changed, 8 insertions(+)

(limited to 'docs')

diff --git a/docs/stanford-naming b/docs/stanford-naming
index e89fbf0..f887a69 100644
--- a/docs/stanford-naming
+++ b/docs/stanford-naming
@@ -122,6 +122,14 @@ Object Naming
         sometimes it's too hard to separate out chunks of a properties
         file.
 
+    <group>-<service>-shibboleth
+
+        The shibboleth.xml configuration file for a service, when it
+        contains some secure data (such as database passwords for shared
+        sessions).  Ideally, the secure data should be stored in separate
+        files and assembled into a shibboleth.xml file, but that isn't
+        always the path of least resistance.
+
     <group>-<service>-ssl-pkcs12
 
         The PKCS#12 file (containing both public and private key) used by
-- 
cgit v1.2.3