Shibboleth Developers

["Howard Gilbert" <>]

I once wrote an AAP in the SP section of code, but it got replaced by Walter
or Scott, presumably because I made a hash of my first shot at it. Anyway,
as I look at the stuff I see this:

> <Attribute AttributeName="urn:mace:dir:attribute-
> def:eduPersonScopedAffiliation"
> AttributeNamespace="urn:mace:shibboleth:
> 1.0:attributeNamespace:uri"><AttributeValue
> Scope="youngvillains.org">Student</AttributeValue>
> </Attribute>

 
>          <AttributeRule Name="urn:mace:dir:attribute-
> def:eduPersonScopedAffiliation" Scoped="true" CaseSensitive="false"
> Header="Shib-EP-Affiliation" Alias="affiliation">
>                  <!-- Filtering rule to limit values to eduPerson-
> defined enumeration. -->
>          <AnySite>
>              <Value>MEMBER</Value>
>              <Value>FACULTY</Value>
>              <Value>STUDENT</Value>
>              <Value>STAFF</Value>
>              <Value>ALUM</Value>
>              <Value>AFFILIATE</Value>
>              <Value>EMPLOYEE</Value>
>          </AnySite>

So my guess is that the code doesn't honor CaseSensitive="false". A quick
look at the code doesn't show anything obvious, or at least that the code
that I think handles this does appear to call equalsIgnoreCase(), so I would
have to create the problem in the debugger to track it down. You could
report it to Scott/Walter while I am getting set up. 

I have added some JUnit code to provide attributes for this kind of testing,
but I am in the middle of shooting another bug now and it requires that I
add the Filter to the mess, and that is my current priority. Since it is
their code they might be able to just look at it and see the problem right
off the top. Otherwise, I will try to create it in test later in the week.