Windows Captive Jetty and the command line

[Rod Widdowson]

As I was going through testing the fixes to a recent bug I spotted a very
minor gotcha with my captive jetty install.

I do not configure an HTTP port on the jetty and so when we come to run any
of the scripts which speak to the IdP (status is what got me, but I suspect
that aacli and others are the same) we do not get access.

I would rather not configure an HTTP port, but I guess I have to?

R