alternate attribute names

[Marvin Addison]

On Mon, Jun 18, 2018 at 5:51 PM Greg Haverkamp <gahaverkamp at lbl.gov> wrote:

> I haven't decided if it's better or worse, but I've lately started using
>> activation conditions for these requests.
>>
>
We've tried many solutions and I'm comfortable saying that activation
conditions are the way to go for one-off attribute names. We're seeing an
uptick in the number of integrations that require specific (and in many
cases non-standard) attribute names, and activation conditions allow us to
focus on these quirks by adding additional attribute encoders that are
toggled with an activation condition as your example demonstrates. If
you're doing consent or other flows that work on attribute sets, you'll
appreciate the benefit of this approach even more.

Marvin at Virginia Tech
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180628/3028097f/attachment.html>