Multi value attribute selection

[Scott Cantor]

> My first idea was to add an intercept that presents and sets the selected value and then influence a AttributeDefinition based on that selection.
> Before I get deeper into this idea I wanted to check if this sounds possible from a conceptual perspective and if someone already has configured
> something alike.

I think the trade-off of that degree of technical debt against forcing such an SP to be compliant through management or purchasing pressure is pretty clear, but that's just me. IAM as a whole has a serious "just say yes" problem.

I would imagine as was suggested that it might be possible to twist the consent feature into some kind of approach that could work, but I think it would be awkward at best presentation-wise, probably depends how large the user population is and how effectively one could explain to them what they were expected to do.

An interceptor is certainly doable (you can manipulate what's inside the AttributeContext if you want to, by that point), but certainly some work that's beyond a lot of people, so it wouldn't be my general sort of recommendation. But, yes, that's what the feature is for.

-- Scott