Jetty configuration roundup for v3

[Tom Zeller]

Here are some options for configuring Jetty for IdPv3 :

(a) manual configuration
(b) a script
(c) jetty-spring.xml (Spring DSL)
(d) jetty-shib.xml (Jetty DSL)
(e) embedded (Java)
(f) start.d/700-shib.ini

Manual configuration is basically what we have today, meaning that
deployers will copy or modify files based on our instructions.

I am not real keen on writing and maintaining a script for Jetty
configuration, mostly because it is one-more-thing-to-maintain. Not
opposed, just not excited.

I have not had much luck with configuring Jetty via Spring, it seems
that the DSLs are different enough that it is not straightforward to
provide an equivalent configuration via Spring.

It also seems not possible to provide a single jetty-shib.xml
configuration using the Jetty DSL, since the DTD prohibits the use of
a single file for configuring SSL as well as the Server.

By "embedded" I mean configuring Jetty in Java, and I do not think
this will be flexible enough for deployers. It also means we would
need to provide our own start|stop scripts, instead of leveraging
Jetty's.

Finally, I am interested in Jetty's new start.d modular start style. I
am hoping we can simply provide a 700-shib.ini file, which will still
allow deployers to turn on setuid or whatever they need.[1] There is a
recent jetty-dev thread where we can provide feedback if we need to.
[2]

Comments are welcome.

[1] https://github.com/eclipse/jetty.project/tree/master/jetty-distribution/src/main/resources/start.d
[2] http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01721.html