langaware option

[Athanasios Douitsis]

Hello Scott, Peter,

Thank you very much for the answers. Yeah, I was the one that actually
asked for something like that some years ago. Strange that nobody else has
asked about it so far. I completely understand this cannot be of priority,
at least not at this point.

Anyway, multivalued attributes are a pain regardless of the specific
language issue. I would be very happy even if there was a totally naive way
to assign the different values of an attribute to different variable names
manually in the SP configuration.

Athanasios

On Tue, Nov 18, 2014 at 6:46 PM, Peter Schober <peter.schober at univie.ac.at>
wrote:

> * Cantor, Scott <cantor.2 at osu.edu> [2014-11-18 17:32]:
> > On 11/18/14, 3:43 PM, "Peter Schober" <peter.schober at univie.ac.at>
> wrote:
> > >
> > >And what this would mean for other SP implementations, which wouldn't
> > >know how to tell those multiple values apart. Of course, if you're
> > >already sending e.g. Greek script/glyphs and latin script as multiple
> > >values of the same attribute you already have that problem.
> >
> > >From a representational point of view, certainly, I get it, just add
> > xml:lang to the AttributeValue element. The trick is how that translates
> > to pulling data from data connectors and somehow knowing the language
> (and
> > I have no idea how this relates to LDAP options).
>
> ACK.
>
> The above was simply meant for the OP to consider dealing with
> non-Shib SPs and how they'd handle multiple values in different
> scripts (assuming those SPs wouldn't already have ways to pick
> out/prefer one xml:lang over another).
> -peter
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Athanasios Douitsis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20141118/5c5bbb04/attachment.html