Nginx note

[davidjb]

Kevin P. Foote wrote
> Just a thought..
> 
> Does the nginx/fcgi via epel get you any closer to maintaining a
> packagable
> solution?
> 
> Even if you have to require epel to use the shib-sp/nginx/fcgi combo I
> think that would be very reasonable for any given installer to manage.

>From the Shibboleth SP side, EPEL certainly makes that packagable -- eg
having the fcgi/fcgi-devel packages available means being able to
compile/run the FastCGI applications.  (eg
https://github.com/jcu-eresearch/shibboleth-fastcgi/blob/master/rebuild.sh)

However, Nginx needs to be patched and custom compiled with certain options
for Shibboleth SP support to be added.  The EPEL version is older at v1.0
versus v1.4, which is where I've done my testing (and what I'm using in
production at present).  It should be possible to use EPEL's package
(assuming the Auth subrequest module supports v1.0) and rebuild it in this
case, but someone would need to test it thoroughly.  The actual
configuration I have within my Nginx instance for enabling Shibboleth
support is a lot of standard boilerplate which could ship with a packaged
solution, but still requires quite a bit of tinkering with header dropping
and possibly location configuration.  I'm open to discussion about this
though from anyone more adept at package management!

As a side note, package maintenance would become easier for Nginx 1.5 as
this custom module is now in the core Nginx code, and only a recompile/minor
patch for Shibboleth is required.  However, I can't vouch for its stability
at present as it's considered 'mainline'.  In the meantime, I'll be
continuing using v1.4.x.





--
View this message in context: http://shibboleth.1660669.n2.nabble.com/Nginx-note-tp7588765p7590156.html
Sent from the Shibboleth - Developers mailing list archive at Nabble.com.