grouping attributes in consent UI

[Tom Zeller]

> but since (last time I checked) per-attribute consent
> had no way of making some of those per-attribute checkboxes
> preselected and read-only (e.g. when isRequired="true" for an attr or
> it's part of the R&S attribute bundle for an R&S SP) I feel
> per-attribute consent is unusable atm.

In addition to per-attribute consent we could consider
per-attribute-value consent, for example, not releasing a particular
group membership. But I thought there was work being done on consent
and all its wonder elsewhere, not sure what happened.

> I guess the grouping also somewow relates to
> shibboleth.consent.attribute-release.AttributeDisplayOrder in
> conf/intercept/consent-intercept-config.xml, when attributes are no
> longer shown in a flat list ordered by this parameter.
> So I guess it would (need to) be another config option?
>
> Ideas, suggestions?

Maybe a map would be better than a list (of attributes in order) and
the keys could be the "groupings".

Tom