CAS attributes in lowercase, missing scope

[Joe Alfonso]

The only reason I was interested was for parity between the two protocols;
it would be nice to be able to say "here's what you'll get for
eduPersonPrincipalName" without regard for the protocol used.

But maybe it's nonsensical to think of these dissimilar protocols this way.

Thanks!

On Wed, Sep 28, 2016 at 10:54 AM, Marvin Addison <marvin.addison at gmail.com>
wrote:

> On Wed, Sep 28, 2016 at 10:10 AM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
>> The underlying objects are ScopedAttributeValue with a separate value and
>> scope, so a simple getValue() doesn't return the scope included.
>>
>
> Yeah, that's the root cause in this case. I didn't have a use case at the
> time for other means of converting an attribute into a string, and
> getValue() was the simple solution. I'm open to additional strategies, but
> honestly I didn't think anyone would have a use case for scoped attribute
> values in the CAS use case where the overwhelming majority of use is within
> institutional boundaries. Feel free to open a Jira improvement issue for
> supporting scoped attributes and I'll do further analysis on feasibility.
>
> M <users-unsubscribe at shibboleth.net>
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160928/5a55d286/attachment.html>