How to change relying-party.xml config location dynamically
Yaowen Tu
yaowen.tu at gmail.com
Tue Jul 23 20:01:02 EDT 2013
Thanks a lot Scott. Can you give me some more details about the plugins?
Where is the sample code that I should look at? Any documents?
Yaowen
On Tue, Jul 23, 2013 at 4:43 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 7/23/13 7:35 PM, "Yaowen Tu" <yaowen.tu at gmail.com> wrote:
>
> >So how can I change the source code to support some kinds of place holder
> >like:
> >
> ><srv:Service id="shibboleth.RelyingPartyConfigurationManager"
> >xsi:type="relyingParty:SAMLMDRelyingPartyConfigurationManager"
> >
> > depends-on="shibboleth.SAML1AttributeAuthority
> >shibboleth.SAML2AttributeAuthority">
> > <srv:ConfigurationResource
> >file="$IDP_CONIFG_HOME$/idp/relying-party.xml"
> >xsi:type="resource:FilesystemResource"/>
> > </srv:Service>
> >
> >
> >When we launch IdP, we make sure IDP_CONFIG_HOME has been set to
> >environment variables. Then in the IdP code, I resolve $IDP_CONIFG_HOME$
> >to translate to the real path.
>
> I don't recall what code handles the Service schema, but the
> ConfigurationResource piece is pluggable. Writing an extension with a new
> resource type would work. The existing ones are in shibboleth-common.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130723/d19a3054/attachment.html
More information about the users
mailing list