<div dir="ltr">Yes, agreed. I like the idea of an OID-Connect httpd module, but having to also run java as a requirement would likely mean not bothering. It would just be easier to use some PHP & the ShibSP ExternalAuth handler to accomplish the same thing.<div>
<br>Dave</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 18, 2013 at 12:40 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> With regard to the design, I am not an Apache HTTPD guru. I have no<br>
> interest in wasting any cycles re-inventing Apache httpd interfaces. The<br>
> Apache plugin is 1/2 the work... we also have to write "oxd" in java,<br>
> to use the existing OX OpenID Connect and UMA client code. I just want to<br>
> see a plugin as quickly as possible...<br>
<br>
</div>Ok, then the primary issue is that I would not likely accept a hybrid implementation.<br>
<br>
I suspect that if you create a design where you basically farm out the work to a separate system via web services, you will have security and efficiency problems, but if you tried to force the overall Apache "solution" to include Java (as we did at one time and could easily have continued to do), you would find some pushback from many on that requirement.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Scott<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>David Langenberg<div>Identity & Access Management</div><div>The University of Chicago</div>
</div>