gss_eap_attr_ctx::registerProvider(ATTR_TYPE_LOCAL, createAttrContext);
+The shibresolver library also has to be loaded as an extension (exact path and filename vary by platform):
+
+ <OutOfProcess logger="shibd.logger">
+ <Extensions>
+ <Library path="plugins.so" fatal="true"/>
+ <Library path="/usr/lib/libshibresolver.so" fatal="true"/>
+ </Extensions>
+ </OutOfProcess>
+
If you then run shibd, mech_eap's use of the SP will be remoted to it in the usual fashion.