Multiple language versions for the same attribute

Description

Hi,

This is a "mirror" RFE for https://issues.shibboleth.net/jira/browse/IDP-102 requesting a corresponding way to decode multiple language versions of the same attribute will be needed on the SP.

Thanks,
Athanasios

Environment

None

Activity

Scott Cantor 
April 2, 2012 at 1:09 PM

Closed with documentation added.

Scott Cantor 
March 30, 2012 at 10:20 PM

http://svn.shibboleth.net/view/cpp-sp?rev=3604&view=rev

Fixed schema, allowed for metadata attribute lang awareness by option to disable decoder caching.

Scott Cantor 
March 29, 2012 at 9:20 PM

http://svn.shibboleth.net/view/cpp-sp?rev=3603&view=rev

Lang awareness implemented in new resolver, extractor, and decoder APIs and decoders all support langAware option to select only the best matching value.

Scott Cantor 
January 21, 2012 at 11:29 PM

I think the better idea is to implement language matching for the values so that the best matching value is used to populate a single valued header. I can factor the logic added for metadata content extraction of language-specific information out into a reusable layer and then add lang awareness to the decoders.

The use case of extracting more than one value and tracking the language could be met by using the non-string decoder options in the SP to encode the lang attribute into the header value. Using different header names would be impossible, since the names would have to depend on the language tag, and it would be trivial to spoof since the set of tags is approximately infinite.

Scott Cantor 
September 2, 2011 at 6:55 PM

Per my list comment, I don't know what this really means in terms of software requirements. I'd suggest opening a thread on that on the dev list.

Fixed

Details

Assignee

Reporter

Original estimate

Fix versions

Created September 2, 2011 at 1:24 PM
Updated April 2, 2012 at 1:09 PM
Resolved March 29, 2012 at 9:20 PM