IdP credentials for delegation Assertion signature validation

Brent Putman putmanb at georgetown.edu
Fri Aug 21 19:53:22 EDT 2015



On 8/20/15 6:36 AM, Rod Widdowson wrote:
> If this doesn't feels like a "RelyingParty" thing you can create a new interface to do what you need, make DefaultRelyingPartyConfigurationResolver implement it and then build your own service based around that.  I have currently swapped the precise details out on how to do this, but it's how the AttributeResolverImpl masquerades as an Attribute Resolver and an Attribute Mapper.

What I did for now, to keep moving forward, was just define a
List<Credential> directly on DefaultRelyingPartyConfigurationResolver. 
Then a specialized credential resolver injected with the service gets
the serviceable component on each call.  It needs to check and cast to
DefaultRelyingPartyConfigurationResolver, so it uses the service
directly (shibboleth.RelyingPartyResolverService), rather than the
facade bean (shibboleth.RelyingPartyConfigurationResolver).  At least
until we decide whether we want to promote this to the
RelyingPartyConfigurationResolver interface.

This turned out to be pretty easy.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150821/ef908c92/attachment.html>


More information about the dev mailing list