resolving attributes from a different OU- best approach?

[Cantor, Scott]

> Initially I thought the best way to do this might be to write a custom
> ShibbolethAttributeResolver that loads the other objects (from the other
> OUs) and then converts them into a readable description.

There's only one resolver instance that's going to run, so that wouldn't work. And you certainly wouldn't want to.

>  That API seems
> relatively straight forward so I think I'd be fine looking into that, but I'm now
> wondering if I can just chain together DataConnectors and handle this via the
> Dependencies support

Connectors can chain or attribute definitions can depend on different connectors. It's a directed graph.

-- Scott