Reading shibboleth IdP configuration from database

[Nanda Kumar]

Thanks for the responses.

My understanding is the following:

1.  I define three different DBResources one each for relying party, attribute resolver and attribute filter implementing the 
     org.springframework.core.io.Resource interface and possibly the net.shibboleth.utilities.java.support.resource.Resource interface.

2.  These three resources will be beans defined in services.xml file with three unique ids.

3.  The p:serviceConfigurations-ref attribute of the beans(services) shibboleth.AttributeResolverService, shibboleth.AttributeFilterService and 
     shibboleth.RelyingPartyResolverService ( in the file services-system.xml) will point to the three DBResources respectively.

This way, the three services will read the configurations from the custom written DB resources.  

Is this correct?

Nanda

====================================================================== 
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient and may contain originating company confidential or proprietary information.  Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, immediately contact the sender by reply e-mail or notify the postmaster at fisc.com and destroy all copies.


-----Original Message-----
From: dev [mailto:dev-bounces at shibboleth.net] On Behalf Of Rod Widdowson
Sent: Wednesday, November 11, 2015 5:15 AM
To: 'Shib Dev'
Subject: RE: Reading shibboleth IdP configuration from database

> Well, the HTTP example(s) are the equivalent. The wiring entirely 
> depends on the implementation, though presumably there's a DataSource 
> somewhere in the mix.

I would add that it is best if your resource implements both org.springframework.core.io.Resource and net.shibboleth.utilities.java.support.resource.Resource

The latter isn't strictly needed for what you are doing, but if you make the change (and their methods are nearly identical) you will be able to plug you Resource into OpenSAML (for things like metadata parsing).

You might find a "Spring resource from DataSource" somewhere out there, but my suggestion is port your V2 to V3 - As Scott said the HTTP example is a good place to go because its precisely that - a port from V2.

Rod

--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net