Shibboleth IdPv3 administrative urls

[Peter Schober]

* Cantor, Scott <cantor.2 at osu.edu> [2015-10-22 17:47]:
> We'll probably get around to replacing the use of java.net.URL,
> which is why the current code doesn't have a way to bypass the cert
> checking on 443 if you just use localhost with that.

OK. But no issue having a listener on 127.0.0.1:80.

> There's also a new environment option in the next version to set the
> base URL for all the scripts.

OK. v3.2 sounds better everytime someone mentions it. :)

> >Reloading works wonderfully and at least on Tomcat8 is absolutely
> >essential, as restarting the IDP (or context) would take ages, so that
> >would be absolutely prohibitive for testing purposes.
> 
> That's diagnosed now, you just have to let it unpack the war. It
> doesn't take appreciably longer than on Jetty.

I never had unpackWAR="false" in the context deployment descriptor for
IDPv3. According to Tomcat docs that setting defaults to true, it was
always unpacked and setting it to "true" explicitly Tomcat still
reports startup time around either 200s or 400-500s.
But maybe I'm complaining about comparatively "good" startup times?
(3 to 8 minutes still is a lot and much longer than v2.)
-peter