Decryption config

[Cantor, Scott]

>Actually, I just realized that doing the chaining that way will cause
>duplicates, and therefore unnecessary processing, due to the static
>resolver being called potentially many times (once for each PublicKey and
>key name seen from the resolved KeyInfo).  What
> I think we actually want is:  the KeyInfoCredentialResolver wired into
>the DecryptionConfiguration would be a chaining one: the first member
>would be the LocalKeyInfo- one I was describing, and the second a
>StaticKeyInfo- one.  The local CredentialResolver
> wired to the LocalKeyInfo- one would just then be a plain
>CollectionCredentialResolver.  You'd presumably just inject the same
>list/set of Credentials into both the StaticKeyInfo- and Collection-
>resolvers.

For clarification, what's the purpose of wiring the two in a chain? Is
that just to prevent the KeyInfo hinting from accidentally precluding any
of the locally configured keys?

The SP has that problem occasionally due to key name conflicts when certs
don't match, so I was assuming that was what you were thinking.

-- Scott