Great. I actually loaded it out-of-process.<div><br></div><div>I appreciate it!<div><br><div class="gmail_quote">2013/1/16 Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 1/15/13 5:48 PM, "Daisuke Miyakawa" <<a href="mailto:d.miyakawa@gmail.com">d.miyakawa@gmail.com</a>> wrote:<br>
><br>
>I have a question about Shibboleth SP extension:<br>
> Can I introduce a new SP Handler implementation, using SP's extension<br>
>mechanism?<br>
<br>
</div>Yes.<br>
<div class="im"><br>
>After putting the shared object in a right directory and rebooting shibd,<br>
>I successfully saw "(constructor): appId=default" log message in my<br>
>shibd.log, which is<br>
>embedded in my implementation of ExtraHandler (as you can see above).<br>
>At this point, I assumed ExtraHandler was detected and loaded by the SP<br>
>appropriately.<br>
<br>
</div>Your handler (in its simple form) is not a shibd extension. It can load<br>
there, but won't do anything, it has to be loaded by the in-process half<br>
to matter. My guess is you loaded it only out of process and your<br>
native.log will show an error trying to install a plugin it can't find.<br>
<div class="im"><br>
>After that, however, I couldn't access to the relevant URL,<br>
>https://(myhost)/Shibboleth.sso/Extra.<br>
>SP raises shibsp::ConfigurationException with saying "Shibboleth handler<br>
>invoked at an unconfigured location."<br>
>though SP already appears to know the Handler is there, according to the<br>
>previous log message.<br>
<br>
</div>No. shibd does, but that's not the whole SP.<br>
<div class="im"><br>
>No relevant error log was seen in shibd.log, while ideally I should be<br>
>seeing "run" log message.<br>
<br>
</div>That isn't where such a message would appear unless your extension is<br>
implemented with internal remoting to an out of process portion like many<br>
of the built-in handlers are. The first "footprints" of any extension<br>
operating as a handler are in native.log from within the web server.<br>
<br>
-- Scott<br>
<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:dev-unsubscribe@shibboleth.net">dev-unsubscribe@shibboleth.net</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Daisuke Miyakawa (宮川大輔)<br><a href="mailto:d.miyakawa@gmail.com">d.miyakawa@gmail.com</a>
</div></div>