Metadata expiry and computing a new expiration time.

Mon Sep 14 09:57:44 EDT 2015

On 9/14/15, 9:48 AM, "users on behalf of Rod Widdowson" <users-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:

>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
>> <html><head>
>> <title>301 Moved Permanently</title>
>> </head><body>
>
>I'd say (but here I am beginning to get out of my comfort zone) that this
>means that you do not have the IdP's container (Jetty/Tomcat) listening on
>port 80 for control information and that some other webserver is serving
>there.  I think you need to specify "-p" to point to wherever it is
>listening.

You can set a port that way (I think), or just set -u to a URL base/prefix that's more appropriate. The default assumes http://localhost/idp is the context root of the IdP webapp. The problem with using https:// is the usual need for a certificate in the Java root store.

One option is just to add a local listener port for HTTP in the container on some port that isn't exposed. Unless you're using remote scripts to invoke the admin tools, you don't really want to change the ACL rule on the admin functions from 127.0.0.1 unless it's really needed.

-- Scott