Transforming remote user attribute at the SP.
Cantor, Scott
cantor.2 at osu.edu
Wed Jul 25 11:38:31 EDT 2012
On 7/25/12 9:34 AM, "Friedrich Clausen" <fred at derf.nl> wrote:
>
>The SP is currently receiving the remote user attribute (eppn) in the
>format user at institution. I have read the docs for the scoped attribute
>decoder and I understand it splits the value using, by default, the
>"@" symbol but I am not sure how to implement this. Is there an
>example somewhere showing how you can extract just the user name?
That isn't what it does. A scoped decoder's job is to capture both parts
properly so that filtering by scope works. The serialized form is exactly
that.
And you would NOT want to drop the scope. That won't be unique and that's
a very bad idea. What is your use case? If it's not a federated
application (so uniqueness isn't an issue), you could just use a
different/custom attribute as an identifier.
-- Scott
More information about the users
mailing list