Reading shibboleth IdP configuration from database

[Tom Zeller]

> On Nov 10, 2015, at 4:34 PM, Nanda Kumar <NKK at FISCHERINTERNATIONAL.COM> wrote:
> 
> Hello,
>   In v2 I got this working by writing a custom DBResource and pointing the ConfigurationResource for each of relying party, attribute resolver and attribute filter services to this new resource.
> This was done by changing the xsi:type of the ConfigurationResource to the DBResource in services.xml file.
> How can I do this in v3?  In v3 services.xml has resources defined like
>  
> <util:list id="shibboleth.RelyingPartyResolverResources">
>         <value>%{idp.home}/conf/relying-party.xml</value>
>         <value>%{idp.home}/conf/credentials.xml</value>
>         <value>%{idp.home}/system/conf/relying-party-system.xml</value>
>     </util:list>
>  
> There doesn’t seem to be a way to extend the type with the above configuration.
> Should I be writing a whole new bean like the FileBackedHttpResource or the HttpResource to handle this?
> Any help in this regard is greatly appreciated.

We use a StringToResourceConverter (in spring-extensions) to convert those Strings to Resources. I’m guessing you would define a <bean/> representing your custom DBResource, and then would need to add it to that list of resources, I’m not sure what that wiring would be off-hand. Over in system/conf/system-services.xml you can see how the list of resources is injected.