"sourceAttributeID was not specified but is required"

[Liam Hoekenga]

On Thu, Dec 1, 2016 at 10:13 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> By definition if the definition is an aggregate of others, it shouldn't be
> of a type that intrinsically can only operate on one.


Are there definitions that don't require a source attribute?

One of our examples is our construction of eduPersonScopedAffiliation
We have multiple campuses, and we wanted to be able to represent them in
ePSA.
Rather than have one giant mapped attribute that could calculate ePSA, we
currently have campus specific mapped attributes that are aggregated under
ePSA:

    <resolver:AttributeDefinition id="eduPersonScopedAffiliation"
xsi:type="ad:Prescoped">
        <resolver:Dependency ref="umichPersonScopedAffiliation"/>
        <resolver:Dependency ref="umichPersonScopedAffiliationAA"/>
        <resolver:Dependency ref="umichPersonScopedAffiliationDBRN"/>
        <resolver:Dependency ref="umichPersonScopedAffiliationFLNT"/>
...
    </resolver:AttributeDefinition>

It made sense at the time we did it.
Do we live with the warning? Are there more appropriate attribute types?

Liam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161201/287e8926/attachment.html>