<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Not sure this message ever came through over the weekend. Had attached a screenshot that I think must have caused it to be blocked. Hope this one reaches out to you. <div class=""><br class=""><div class="">
- Misagh
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Misagh Moayyed <<a href="mailto:mmoayyed@unicon.net" class="">mmoayyed@unicon.net</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">Re: Idp v311 installation at non-default loc</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">May 23, 2015 at 11:44:52 PM GMT+4<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Shib Users <<a href="mailto:users@shibboleth.net" class="">users@shibboleth.net</a>><br class=""></span></div><br class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Well, given Brent’s explanation, the “template config” may be a moot clarification now :) but I had in mind that if I needed to write up additional PropertySource elements in the Spring XML configuration, it would have made my job a lot easier if there was already a template, commented out, in the appropriate XML file that said “Uncomment this block and set this X to Y if you need to do Z”. Obviously, this does not apply. <div class=""><br class=""></div><div class="">Brent, I am glad you brought up context params because that’s exactly what I had in mind. I have written extensions of the initializer in the past, and I know for certain that the context is initialized with the parameters when the initializer runs. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">To resolve the chicken-and-egg problem, an alternative would be:</div><div class=""><br class=""></div><div class="">1. Modify the web.xml to provide a setting for IdP.home</div><div class="">2. The Initializer will look at the default location, and if no IdP is found, it will look at the path specified by that context param</div><div class="">3. The installer will pre-populate that parameter with the input received from the user.</div><div class=""><br class=""></div><div class="">In fact, this can be made such that you always read from the context param, and so regardless of what value I provide during the setup, the deployment of it will simply “just work” with no additional (and perhaps duplicate) changes. Populating the web.xml should also be perfectly possible, as the build does (or v2 did) various kinds of regex ops on the config, and this would be no exception. </div><div class=""><br class=""><div class="">- Misagh<br class=""></div><br class=""><blockquote type="cite" class="">On May 23, 2015, at 7:42 PM, Rod Widdowson <<a href="mailto:rdw@steadingsoftware.com" class="">rdw@steadingsoftware.com</a>> wrote:<br class=""><br class="">As Brent says, a non standard idp.home has to be configured *outside* of the IdP (as Brent said) - it’s a required part of bootstrapping the IdP.<br class=""><br class=""><blockquote type="cite" class="">It might be easier if you had template config in the configuration for additional property resources <br class=""></blockquote><br class="">Again, like Brent I am not really sure what you mean by this. But any other property can be merged in at run time. This is primarily aimed at systems which do automated installations (our own windows MSI installer does it)<br class=""><br class="">You should look at the copious comments at the top of bin/build.xml, but the summary is that if you define (on the build command line) a property idp.merge.properties to be a property file then its contents will be merged into the idp.propererties.<br class=""><br class="">% install.bat -Didp.merge.properties=<propertyFile><br class=""><br class="">/Rod<br class=""><br class="">-- <br class="">To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" class="">users-unsubscribe@shibboleth.net</a><br class=""></blockquote><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>