Version 3.4 metadata driven overrides

[Cantor, Scott]

On 10/23/17, 7:49 PM, "dev on behalf of Michael A Grady" <dev-bounces at shibboleth.net on behalf of mgrady at unicon.net> wrote:

> Yes. I have to say, I work with a lot of institutions, and almost none have even had any attribute in their directory to indicate
> "elected FERPA suppression" or some related suppress-type indicator.

And I thought we were pretty backward when it comes to FERPA...

> So I've rarely seen it's use in attribute filter files.
> But it would be easy to say, "if you want to suppress sending attributes for a person", create an attribute id "suppress" with a
> value of true (or "yes"). And then have an entity attribute activated config in the filter that looks for that id/value, and an
> entity attribute of "honor suppression", and have that deny all the attributes that one creates entity attribute-based release
> rules for.

Maybe we could do something a little more elegant like have two different properties:

- release all values
- relase all values if not suppressed

And then have the values contain the attribute IDs to apply them to as you suggested.

Honestly though the real point of defining some kind of default framework for FERPA was to be able to release certain attributes by default. Don't know if that's still on the table.

-- Scott