Attribute consent flow activation based on relying party and user attribute

[Wessel, Keith]

We're wanting to trigger user attribute release consent based on a set of conditions involving both the SP (or entity tag) and/or the user's FERPA suppression state. I know I can do the first in the relying party config, and I know I can do the second in a custom bean profile-intercept.xml. But I'm trying to figure out if it's wise/necessary to use these two different files.

Should I possibly be triggering consent based on relying party in the profile-intercept.xml so I can have my logic in the same place as the attribute-based activation? That sounds as messy as trying to write a custom bean that activates based on FERPA suppression attributes in relying-party.xml. After all, an attribute indicating a user is FERPA-suppressed has nothing to do with relying parties.

Just thought I'd ping the list for a sanity check before I modify both of these files.

The end goal is to have some requests activate the consent flow for all users, others for only FERPA-suppressed users, and others not at all, based on the SP or SP tags.

Keith