Configuring an Aggregate DN Resolver with IdP 4.0.1

[Max Spicer]

Thanks, Scott. On closer examination, there are a couple beans in my config
that I can remove, but most do seem to be required for this setup.

I wasn't aware of chaining validators as an alternative solution to this.
I'll make sure that we look at this when we switch to 4.1 rather than
attempting to carry over our current setup.

Max

On Wed, 3 Feb 2021 at 17:55, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 2/3/21, 12:17 PM, "users on behalf of Max Spicer via users" <
> users-bounces at shibboleth.net on behalf of users at shibboleth.net> wrote:
>
> > The docs do suggest that this will be necessary, but the example I was
> following does not show this explicitly and I can't
> > help wondering if I am missing a trick.
>
> Well, I don't know anything about the underlying objects but at the end of
> the day the only real trick is to inject (in that particular example) the
> aggregateAuthenticator bean into the authenticator property of the
> LDAPValidator bean that's being used.
>
> The rest would depend on the specifics of the chain of objects that the
> example happens to assume are used, but I would only add exactly the
> objects that the chain of wiring actually references. It may be that's
> everything, but I would hope not. And if it is, upgrades are going to be
> painful.
>
> That alone would lean me to say, as I keep saying, avoid the tricks and
> just chain validators together with whatever different options they need
> and run them in series.
>
> -- Scott
>
>
>

-- 
Max Spicer, IT Services, University of York
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210204/01fffe89/attachment.htm>