SAML artifact config support

[Rod Widdowson]

I looked at the files and I remember - the issue was working how to inject
the <context:property-placeholder> statement.  

In my testing I just nested my custom schema inside a <beans> statement so I
could inline the property place holder.  Since the issue was about seeing
whether substitution could be made to work without factory beans (it does) I
stopped at that point.  I suspect that for our configurations we can achieve
much the same by injecting two Resources into the spring context, one with
the property-placeholder and one with our syntax in it.

Now that the configuration for the Attribute resolver is done it seems like
a suitable time to get this finalized and maybe code up an example. Into
idp-testbed.

Watch this space.

Rod




> -----Original Message-----
> From: dev-bounces at shibboleth.net [mailto:dev-bounces at shibboleth.net]
> On Behalf Of Cantor, Scott
> Sent: 17 December 2013 19:04
> To: Shib Dev
> Subject: Re: SAML artifact config support
> 
> On 12/17/13, 1:49 PM, "Rod Widdowson" <rdw at steadingsoftware.com>
> wrote:
> 
> >
> >> One question I had, Rod, did you ever manage to get a property
> >>replacement
> >> to work with a custom config schema?
> >>
> >
> >Yes, I cannot remember the details but I will dig out the mail tomorrow.
> >If you look in the tests for idp-core there is a package called 'nature
> >study' which has the examples of this working, as I recall there was some
> >slight manipulation needed..
> 
> It's not crucial here, but it's the most likely way to easily support two
> IdP nodes pointing SPs back at a dedicated artifact lookup URL to avoid
> the clustering requirement, by overriding just the index property (which
> could probably come from an environment or system variable I'm guessing).
> 
> -- Scott
> 
> 
> --
> To unsubscribe from this list send an email to dev-
> unsubscribe at shibboleth.net