Jetty + REMOTE_USER

Jim Fox fox at washington.edu
Thu Sep 10 12:51:20 EDT 2015


The documentation also states, (several places): "Apache Tomcat 8 (officially supported)"

I'll note that the project team don't use Apache in front of Jetty either. 
And I need and like to have the IdP run behind Apache.

Jetty: 1) Doesn't support AJP, and 2) it's configuration is a bowl of spaghetti, to me anyway.

Tomcat: 1) Suports AJP, 2) I already know how to configure it.

I do implement the suggestions on the tomcat page:

   https://wiki.shibboleth.net/confluence/x/JQAUAQ

and find the IdP starts up in about 30 seconds.  Good enough for me.


I try to be as standard as is feasible.

Jim


On Thu, 10 Sep 2015, Matthew Slowe wrote:

> Date: Thu, 10 Sep 2015 09:31:38
> From: Matthew Slowe <m.slowe at kent.ac.uk>
> To: Shib Users <users at shibboleth.net>
> Reply-To: Shib Users <users at shibboleth.net>
> Subject: Re: Jetty + REMOTE_USER
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, Sep 10, 2015 at 08:40:25AM -0700, Jim Fox wrote:
>> Stick with tomcat.  That's what I do.
>
> I'm trying to be as standard as possible... and the documentation says:
>
> "The recommended container implementation is Jetty and all development
> and most testing time by the core project team is confined to the Jetty
> platform."
>
> I am certainly more familiar with Tomcat's vagaries ;)
>
> - --
> Matthew Slowe | Server Infrastructure Officer
> IT Infrastructure, Information Services, University of Kent
> Room S21, Cornwallis South
> Canterbury, Kent, CT2 7NZ, UK
> Tel: +44 (0)1227 824265
>
> www.kent.ac.uk/is | @UnikentUnseenIT | @UKCLibraryIt
> PGP: https://keybase.io/fooflington
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEARECAAYFAlXxsGoACgkQ/V1qDCaTXgc9YACeKonsqgCG1laX5nHPEghexPbP
> PQkAniVnp0D27jqaVb4bAX5UXuxS7WHw
> =wHBq
> -----END PGP SIGNATURE-----
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>


More information about the users mailing list