I am recieving a WARN when two DataConnectors export the same attribute.
(Think of eduPersonAffiliation, with "member" from a static DC, and the
rest from an LDAP DC.)
2020-12-29 15:24:26,934 - WARN
Attribute Resolver 'ShibbolethAttributeResolver': could not export
attibute 'eduPersonAffiliation' from data connector 'staticAttributes'
since an attribute of that name already exists.
There's no explicit AttributeDefinition for eduPersonAffiliation in the
Is this intended behaviour? The Wiki currently tells otherwise, defining
a clash as: Data Connector exports an attribute with the same name as an
Dr. Martin Haase, Solutions Engineer
DAASI International GmbH
The only thing that get merged are explicit attribute definitions. This warning is the principal of least surprise. It is
important now, but it was vital when we still thought that exportAll (not thoroughly deprecated) was a good idea.
> Like Scot says this is one of the odd edge cases which give a need for simple attribute definitions.