Windows Captive Jetty and the command line

[Cantor, Scott]

On 11/3/14, 2:48 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>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?

Do you mean not tracking it in some other spot?

Obviously you have to configure Jetty itself...

I suppose it would be a nice thing to have this someplace to maybe feed 
into the scripts, maybe we could do an environment variable for the base 
URL of the IdP for the command line tools?

For the moment I just use http://localhost as the default.

-- Scott