Attribute resolution for private credentials in subject
joller.lee at gmail.com
Wed Apr 6 21:22:04 EDT 2016
My code above does make some assumptions, as Scott pointed out.
In the example code on the wiki, there are always checks for nulls.
I guess that's a good practice,
although I don't know in what situation not checking for nulls might break
or what to do when something is null.
On Thu, Apr 7, 2016 at 8:29 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 4/6/16, 8:19 PM, "users on behalf of joller lee" <
> users-bounces at shibboleth.net on behalf of joller.lee at gmail.com> wrote:
> >It's been quite a while, but someone reminded me that I hadn't posted my
> solution here.
> >So, here is mime, and any better one is appreciated:
> Just that it's making some assumptions about the subject count/order and
> not checking for nulls, so whether that's sufficient is really a local
> -- Scott
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users