Upgrade IdPv3.2.0 doesn't like property placeholders.

[O'Dowd, Josh]

>
> I know it manipulates the property files on initial install, but I didn't think it did on upgrades.

Understood...  The upgrade piece definitely has a dependency to resolve the idp.properties file during execution, though.  I should have anticipated this.

-Josh

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, November 18, 2015 11:52 AM
To: Shib Users <users at shibboleth.net>
Subject: Re: Upgrade IdPv3.2.0 doesn't like property placeholders.

On 11/18/15, 1:30 PM, "users on behalf of O'Dowd, Josh" <users-bounces at shibboleth.net on behalf of Josh.O'Dowd at mso.umt.edu> wrote:



> 
>I do understand why the error, ‘…Could not resolve placeholder 'umt.idp.entityID' in string value "%{umt.idp.entityID}"…’, is happening.  In our case, we are using a couple of these placeholders in the idp.properties file to specify server-environment-specific values, such as entityID.  We are setting those values in the Jetty start.ini file on each server.  Those values obviously are not available to the installation script.

We probably could set up some kind of OPTS variable to use to set them via the shell.

> 
>This is just an FYI that the docs don’t indicate this.  Maybe this is a weird practice that doesn’t warrant a warning in the docs.

I know it manipulates the property files on initial install, but I didn't think it did on upgrades.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net