Fwd: Idp v311 installation at non-default loc

Misagh Moayyed mmoayyed at unicon.net
Tue May 26 15:15:52 EDT 2015


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. 

- Misagh

> Begin forwarded message:
> 
> From: Misagh Moayyed <mmoayyed at unicon.net>
> Subject: Re: Idp v311 installation at non-default loc
> Date: May 23, 2015 at 11:44:52 PM GMT+4
> To: Shib Users <users at shibboleth.net>
> 
> 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. 
> 
> 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. 
> 
> 
> To resolve the chicken-and-egg problem, an alternative would be:
> 
> 1. Modify the web.xml to provide a setting for IdP.home
> 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
> 3. The installer will pre-populate that parameter with the input received from the user.
> 
> 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. 
> 
> - Misagh
> 
>> On May 23, 2015, at 7:42 PM, Rod Widdowson <rdw at steadingsoftware.com <mailto:rdw at steadingsoftware.com>> wrote:
>> 
>> 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.
>> 
>>> It might be easier if you had template config in the configuration for additional property resources 
>> 
>> 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)
>> 
>> 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.
>> 
>> % install.bat -Didp.merge.properties=<propertyFile>
>> 
>> /Rod
>> 
>> -- 
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net <mailto:users-unsubscribe at shibboleth.net>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150526/def829c8/attachment-0001.html>


More information about the users mailing list