skipping duplicate Attribute mapping (same name and nameFormat)

Cantor, Scott cantor.2 at
Thu Sep 4 10:28:17 EDT 2014

On 9/4/14, 4:22 PM, "Cantor, Scott" <cantor.2 at> wrote:
>Stop supporting targeted ID, that would be my suggestion. Enable the
>special decoder we provided to turn that into the proper syntax that
>should be used in all cases, and use that as the required form that you're
>keying off. That was the point of adding it.

This, BTW, is of course meant to happen as part of a one-time migration in
your application data so that it lines up, as noted on the
eduPersonTargetedID page in the wiki explaining the mess we accidentally

Basically, you take any scoped values you might have stored, chop the
domain, turn the value into whatever serialization you choose to use in
the regular rules (e.g. value!IdP!SP or whatever) and then you're ready to
turn off the original targeted-id support and use the newer Decoder in its
place. That will handle any IdPs that send you the broken form and hide
that from the application.

-- Scott

More information about the users mailing list