R&S surName vs sn

[Tompkins,Charles R]

On 03/27/2013 04:33 PM, Tom Scavo wrote:
> On Wed, Mar 27, 2013 at 4:27 PM, Tompkins,Charles R <crt at ufl.edu> wrote:
>>
>> I am researching R&S for IdP and need a little clarification.
>>
>> Referencing this document: Configure a Shibboleth IdP to Support R and S
>> (https://spaces.internet2.edu/display/InCCollaborate/Configure+a+Shibboleth+IdP+to+Support+R+and+S),
>> I see the example titled "Configure a New AttributeFilterPolicy".  It
>> has the following line:
>>
>> <AttributeRule attributeID="surName">
>>
>> However, when I check the "InCommon Federation Attribute Summary"
>> (http://www.incommon.org/federation/attributesummary.html), I see the
>> attribute "sn" defined, but not "surName".
>>
>> Is this just a documentation typo or will I need to present "surName" in
>> the assertion to R&S SP's?
>
> I don't believe the value of 'attributeID' matters as long as it's
> consistent in the IdP's configuration. (On the wire, the name of the
> attribute is actually based on an opaque OID.)
>
> Tom

Thanks Tom.  I have already defined "sn" so I will go with that.  It 
threw me off to have the others line up except that one.

Regards,
-Charles

-- 
Charles R. Tompkins
UF Information Technology
CNS/Open Systems Group