Attribute resolver questions

[Rod Widdowson]

> a) in services.xml, idp.service.attribute.resolver.resources is
> a list of files so multiple files can be specified. Is it legitimate to
> have the same id (in AttributeDefinition) in more than one files? Tests
> showed that no error/warning is thrown in the logs and that the last
> definition overrides all others. Is this the intended behavior?

Rather I would say that the behaviour when multiple Attribute Definitions or Data Connectors have the same ID is unspecified.   This
is code for "it might work but if it stops working we won't listen to a bug report".
 
> b) is there a way to configure attribute resolver files per relying party?
> i.e. attribute-resolver.xml for shibboleth.DefaultRelyingParty and
> attribute-resolver-override.xml for a relying party in
> shibboleth.RelyingPartyOverrides list.
> 
> c) is there a way to configure attribute resolver files per profile?
> i.e. attribute-resolver-cas.xml for the CAS profile and
> attribute-resolver.xml for all the others.

Not without a significant amount of changes to the spring wiring, much of which is located in the system directory and so not up for
grabs.

My suggestion would be that you look at attribute definitions and data connectors with activation conditions.

Rod