metadata driven configuration - attribute-resolver activation conditions?
cantor.2 at osu.edu
Wed May 1 16:27:29 EDT 2019
On 5/1/19, 4:19 PM, "users on behalf of Liam Hoekenga" <users-bounces at shibboleth.net on behalf of liamr at umich.edu> wrote:
> ...that it can be used with relying-party.xml and attribute-filter.xml, but has any consideration been given to allow it to
> be used w/ activationConditions for attribute definitions and data connectors in attribute-resolver.xml?
You can use EntityAttributes anywhere/anyway you want. The use of them in the filter rules is as arbitrary and open-ended as using them in the resolver would be. The use of well-defined property names that corrrespond to defined Java properties in the ProfileConfiguration and RelyingPartyConfiguration interfaces and classes, and the special wiring supplied, are the only part that is "special" in any particular sense, and even that's not hardwired in any particular way or with those names, they're just pre-defined to make it a standardized approach.
More information about the users