Newbie question: Passing attributes from ADSF through Shibboleth

[Peter Schober]

* Griffin Cheng [CLIB] <cscheng at cpce-polyu.edu.hk> [2013-10-30 10:59]:
> Hello,
> 
> I construct a small "attribute-map.xml" file to extract attributes from the institution's ADSF as follows:
> 
> <Attributes xmlns="urn:mace:shibboleth:2.0:attribute-map" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> 
>     <Attribute name="urn:oid:1.3.6.1.4.1.5923.1.1.1.6" id="eppn">
>         <AttributeDecoder xsi:type="StringAttributeDecoder"/>
>     </Attribute>
> 
>     <Attribute name="urn:oid:1.3.6.1.4.1.5923.1.1.1.9" id="ePSA">
>         <AttributeDecoder xsi:type="ScopedAttributeDecoder" caseSensitive="false"/>
>     </Attribute>
> 
>     <Attribute nameFormat="http://schemas.xmlsoap.org/claims" name="urn:oid:2.5.4.9" id="street"/>
> 
> </Attributes>

> I can see the values [eppn] and [ePSA] fine.  However, the value of
> the "street" attribute is missing.  The ADSF admin claims that the
> test account should have the "street" value added.

Look at your shibd.log, possibly on DEBUG, it will tell you exactly
what it did what all attributes, and why.

If I had to guess I would say that the attribute name is wrong, it
will likely not be called "urn:oid:2.5.4.9" on the wire if you had to
adjust the nameFormat to be something else than URI.

> Do I have to add the "street" attribute also to the metadata
> provider? If so, what should it look like?

"Also"? You don't configure attributes in a MetadataProvider at all.
-peter