From: https://me.yahoo.com/a/9s1IqWsahpHPqgBknM7zgI4SqW.p#29ad7 <Interested_Bystander@web>
Date: Sat, 11 Jun 2011 20:02:29 +0000 (-0400)
Subject: (no commit message)
X-Git-Url: http://www.project-moonshot.org/gitweb/?p=devwiki.git;a=commitdiff_plain;h=30e9fc1c5880dd8034d148ae0d0a9487fdc7b88f

---

diff --git a/prepare.mdwn b/prepare.mdwn
index 114980f..e85f97b 100644
--- a/prepare.mdwn
+++ b/prepare.mdwn
@@ -104,3 +104,22 @@ Other XML attributes defined for the <GSSAPIAttribute> element:
 
 * authenticated="true|false" - allows processing to proceed only if the GSS attribute is authenticated
 * binary="true|false" - treats the GSS attribute as binary-valued
+
+### Daemon Use
+
+To move processing (and significant startup cost) outside of the GSS server process, you can patch mech_eap as follows:
+
+    --- a/moonshot/mech_eap/util_shib.cpp
+    +++ b/moonshot/mech_eap/util_shib.cpp
+    @@ -417,8 +417,7 @@ gss_eap_shib_attr_provider::initWithJsonObject(const gss_eap
+     bool
+     gss_eap_shib_attr_provider::init(void)
+     {
+    -    if (SPConfig::getConfig().getFeatures() == 0 &&
+    -        ShibbolethResolver::init() == false)
+    +    if (ShibbolethResolver::init(SPConfig::InProcess) == false)
+             return false;
+ 
+         gss_eap_attr_ctx::registerProvider(ATTR_TYPE_LOCAL, createAttrContext);
+
+If you then run shibd, mech_eap's use of the SP will be remoted to it in the usual fashion.