Wiring PopulateSignatureSigningParameters ?
Cantor, Scott
cantor.2 at osu.edu
Thu Apr 3 15:00:16 EDT 2014
On 4/3/14, 2:55 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>I haven't looked at any of this, but couldn't you just wire in a
>Static*Resolver for now and change it when I have the Basic- one working?
> Of course you'd have to summon up the signing credential, etc, to inject
>in to the static resolver, so that would obviously have to be faked up.
>But you could a least move "more forward" that way.
We could, yes.
>I guess it's just a question of which bits you go back in and change
>later.
Yes, I just didn't really need to spend the time, since I'm pretty
experienced now with the way contexts all fit together. Once the resolver
returns something, it will all fall into place fine downstream. The bits
left to iron out will be error handling details.
>Yeah, frack. I was thinking/hoping that those would all just be beans
>wired from plain Spring beans files, etc, and the IdP wouldn't have to
>actually know about them. Or maybe they'd be in -spring modules, where I
>thought we relaxed the no-depending-on-impls policy.
I guess that's true, I forgot if we were allowing that.
As far as how it would be done, I think that's largely a compatibility
matter. To support the current schema, we need to be able to manufacture
them in the parsing code. What we do outside compatibility remains to be
seen I guess, but we were mostly focused on splitting up that file, not as
much changing its syntax unless necessary.
-- Scott
More information about the dev
mailing list