user consent, which SPs should trigger these screens ?

[Tom Zeller]

>> We're starting to converge on this too. Does anyone have working code to share yet that toggles the consent flow on based on a directory-suppress user attribute?
> 
> The predicate used in the context-check example flow is a built-in class that can evaluate the context tree and check for a resolved attribute or value and you could apply it directly as an activationCondition in some other spot if you wanted to.
> 
> The context-check flow is an intercept that itself runs a Predicate<ProfileRequestContext>, but any intercept flow (or dozens of other things) can have an activationCondition and the signature is pretty much always just Predicate<ProfileRequestContext>.

Looking at how to implement this, it seems the deployer would want to AND their activationCondition predicate with the default/system predicate. But in this case I don’t see an easy way to do that without copying the default/system activationCondition, since it is wired as an inner bean. Perhaps an improvement would be to remove the inner-ness of the default/system activationCondition, so that it could be referred to in an AND, and would ’survive' updates.