mapped attribute

[Cantor, Scott]

On 3/31/17, 1:55 PM, "users on behalf of Mary Wiegand" <users-bounces at shibboleth.net on behalf of mwiegand at bastyr.edu> wrote:

> I’m sure I’m missing something but, does anyone know if you have to use the two value maps or if you can use just one?

The documentation states that the cardinality of <ValueMap> is 1 or more.

> Does the dependency have to be the id of the attribute you’re trying to map?

Dependency is a messy feature that has design flaws and is very confusing, it depends on what you're trying to depend on. If you depend on a DataConnector, then it points to the connector, and the sourceAttributeID is the attribute from the data connector to use. If you depend on an AttributeDefinition, then it points to the definition and sourceAttributeID is probably ignored. Rod would have to answer that, he's been cleaning all that up so we can replace Dependency.

> And for the AttributeEncoder what should the name be pointing to since the return value isn’t a real attribute in my ad?

I don't understand the question, an AttributeEncoder is identifying the name on the wire to use for the AttributeDefinition it's sitting inside of.

-- Scott