UpperCase Attribute

[Kidd, Don W.]

I tried to convince the SP vendor that they should have to do an toUpper when they get it or just leave everything as lower, but they said we should UpperCase them, so that is what I am trying to do...  

Scott, thanks for mentioning the URL, I need to update that, looks like that URL got lost in the shuffle at one point..  I need to find that old doc...

Don

--------
Don W. Kidd
Senior Systems Analyst
Information Technology Services
Office : 513.529.9655
EMail: dkidd at muohio.edu

On Dec 2, 2011, at 3:14 PM, Cantor, Scott wrote:

> On 12/2/11 2:54 PM, "Peter Schober" <peter.schober at univie.ac.at> wrote:
> 
>> * Kidd, Don W. <kidddw at muohio.edu> [2011-12-02 20:38]:
>>> I am connecting our IDP to a new SP, and they expect our EPPN to be
>>> in Uppercase, is there a way to uppercase an attribute in
>>> attribute-filter?
>> 
>> There's simply no such requirement in the eduPerson spec, so if that's
>> a requirement of the SP I'd say the party running the SP should
>> perform whatever processing they feel necessary in their own code.
>> (If the SP is actually yours and you're trying to work around some
>> specific problem that's something else.)
> 
> Certainly true, but also commonly just one of those things. The SP of
> course doesn't care about EPPN, they just want "userid".
> 
> The main point is you shouldn't use the EPPN attribute you're already
> supporting. If you have to special case it, use a different attribute (as
> your script was attempting) so that it's clearly custom. Bonus points for
> naming it http://muohio.edu/attribute/service/paininneck
> 
> Substitute an appropriate body part for neck.
> 
> -- Scott
> 
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net