decoders for eduPersonTargetedID

[Cantor, Scott]

On 10/25/12 7:32 PM, "Selvaraj, Dineshkumar (ELS-DAY)"
<dineshkumar.selvaraj at lexisnexis.com> wrote:

>Hi ,
> 
>Below two forms of attributes were not able to be decoded by single
>decoder
> 
>1. StringAttributeDecoder decodes the below attribute, but
>NameIDAttributeDecoder fails to decode the attribute as there is no
>NameID in the attribute value

I'm not sure why you're reposting this here, but nothing's changed. You
are showing two examples, one of which is *invalid*. That is the issue.
There's nothing for you to fix. The string case is wrong. It's not even
globally unique, so by definition it isn't valid as an ePTID value. The
IdP sending it to you is operated by somebody who has misconfigured their
software, that's all.

> 
>I tried using both the decoders in attribute-map.xml, but the decoder
>associate with first occurrence of matching
>name(urn:oid:1.3.6.1.4.1.5923.1.1.1.10) and id(eduPersonTargetedID ) was
>taken for decoding. Is there a decoder which can parse above 2 types of
>attributes, irrespective of the attribute value is string or NameID ?

The answer is no, the same as when you asked before.

In theory, one could build such a decoder or a chaining decoder that
executes more than one until something works. There haven't been any
attribute use cases necessitating it because attributes are generally
uniform in syntax and self-limiting as to that syntax.

-- Scott