[JIRA] Updated: (IDP-70) Provide supported and documented way to customize Velocity binding templates used by the encoders

[Chad La Joie (JIRA)]

     [ https://issues.shibboleth.net/jira/browse/IDP-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chad La Joie updated IDP-70:
----------------------------

    Component/s: SAML2
                 SAML1

> Provide supported and documented way to customize Velocity binding templates used by the encoders
> -------------------------------------------------------------------------------------------------
>
>                 Key: IDP-70
>                 URL: https://issues.shibboleth.net/jira/browse/IDP-70
>             Project: Identity Provider
>          Issue Type: Improvement
>          Components: SAML1, SAML2
>            Reporter: Brent Putman
>            Assignee: Chad La Joie
>            Priority: Minor
>
> Several people have asked about doing this, esp. people who customized the IdP.jsp in 1.3.
> People can crack open the opensaml jar, but that's bad.
> Seems to me we ought to be able to document this as some combination of configuration on the VelocityEngine bean shibboleth.VelocityEngine (e.g. use of different resource loaders, and/or a different resource.loader order, etc) and/or changing the template ID's on the encoder beans. People could then use their own jars or directories of templates.
> Only downside is that currently all this is in internal.xml, which people aren't supposed to touch. We could possibly use some levels of indirection to put some of these properties in external files specifically intended to be modified by the user, e.g. PropertyPlaceholderConfigurer and PropertyOverrideConfigurer.
> http://static.springframework.org/spring/docs/2.5.x/reference/beans.html#beans-factory-extension-factory-postprocessors
> Or just do some more custom Spring config schema.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira