Thanks
RobL
Can I check I understand this right? From what I understand the user
tries to access and Shibboleth restricted resource, Apache redirects the
user away to the Identity Provider to authenticate themselves and then
when they are redirected back Apache adds this additional header to each
subsequent request to Mongrel? Or is it a header that is added by the
client and sent through with each subsequent request until they are
logged out?
I guess your application deals with the user once they are already
authenticated and that work is done outside of they rails app. Do you
have any sample configuration for the Shibboleth setup? I've seen
something called saml2ruby which has been used to interface with the
service provider directly, and I guess setting those headers in another
way its not greatly documented and I guess not required if Apache can do
everything for you.
Is this just for Apache, I think this client uses Nginx and that might
be a problem?
Thanks again
RobL
Just pinging the list (again, but a year later!) to see whether anyone
has advice on validating users via Shibboleth on a Ruby application
using Nginx and Mongrel.
I've searched but not found instructions on how to do this.
Would someone please let me know if they have a resource for
implementation of Shibboleth on a Ruby / Nginx / Mongrel setup?
Thank you!
Hi,
Just pinging the list (again, but a year later!) to see whether anyone
has advice on validating users via Shibboleth on a Ruby application
using Nginx and Mongrel.
I've searched but not found instructions on how to do this.
Would someone please let me know if they have a resource for
implementation of Shibboleth on a Ruby / Nginx / Mongrel setup?
Thank you!
Joe
https://github.com/toyokazu/rack-saml
While it supports only a part of Shibboleth SP functions, you can use it
without Apache or IIS frontend.
It was written to be used with omniauth-shibboleth.
https://github.com/toyokazu/omniauth-shibboleth
FYI
Best Regards,
--
Toyokazu AKIYAMA