How to change relying-party.xml config location dynamically
Paul Hethmon
paul.hethmon at clareitysecurity.com
Tue Jul 23 20:33:27 EDT 2013
Yaowen,
Got to wiki.shibboleth.net and follow the menus to find the information on writing plugins. That same information will guide on where you could choose to modify the existing source code.
I would strongly recommend writing a plugin. You'll do more work, but you will only do it once, rather that for every release.
Paul
From: Yaowen Tu <yaowen.tu at gmail.com<mailto:yaowen.tu at gmail.com>>
Reply-To: Shibboleth Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Date: Tuesday, July 23, 2013 8:21 PM
To: Shibboleth Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: Re: How to change relying-party.xml config location dynamically
I hope it is better to change the source code directly, because most likely it will be a generic place, once I change it, the same place holder can be applied to any ConfigurationResource values that defined in other places.
So can anyone give me some hint about where it is?
Yaowen
On Tue, Jul 23, 2013 at 5:01 PM, Yaowen Tu <yaowen.tu at gmail.com<mailto:yaowen.tu at gmail.com>> wrote:
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<mailto:cantor.2 at osu.edu>> wrote:
On 7/23/13 7:35 PM, "Yaowen Tu" <yaowen.tu at gmail.com<mailto: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<mailto:users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130724/52dcd7ca/attachment-0001.html
More information about the users
mailing list