IdP credentials for delegation Assertion signature validation

[Cantor, Scott]

With footnote:

[1] https://jira.spring.io/browse/SPR-4292

On 8/23/15, 2:07 PM, "dev on behalf of Cantor, Scott" <dev-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

>On 8/21/15, 8:00 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>
>>Hmmm, this bean syntax turns out to not work.  I thought that beans defined inside a util:list or other util: collections were still directly referenceable by bean name as long as they carried an 'id' attribute, but the above does not seem to work, i.e. some other wiring of security config spits errors on start that it can't find the bean named shibboleth.DefaultSigningCredential.    I've searched a bit, I can't find a definitive answer yet.  Does anyone else happen to know one way or another?
>
>Closest answer seems to be [1]. Assuming that's still accurate, guess not.
>
>>For now, I punted and just defined the list like so, leaving the existing credential as a "top-level" bean:
>>
>>
>>    <util:list id="shibboleth.SigningCredentials">
>>        <ref bean="shibboleth.DefaultSigningCredential" />
>>    </util:list>
>>
>>I don't know, maybe that's a cleaner syntax anyway, and would be easier for a deployer to retroactively add after an upgrade.  Just copy/paste.
>
>Probably. Obviously you'd have to conditionally reference that since it won't be present on older configs.
>
>-- Scott
>
>-- 
>To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net
>