Upgrade IdPv3.2.0 doesn't like property placeholders.
O'Dowd, Josh
Josh.O'Dowd at mso.umt.edu
Wed Nov 18 13:30:06 EST 2015
The docs at https://wiki.shibboleth.net/confluence/display/IDP30/Upgrading do not indicate that using property placeholders in the conf/idp.properties file will cause an error in the install.sh/.bat script if they happen to be System properties...
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.
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.
As always, thanks for your time.
Josh O'Dowd
Systems Analyst, Developer
Central IT, University of Montana
(406)243-6283
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151118/da6c9458/attachment.html>
More information about the users
mailing list