Best practice MFA IdP3.3.1

[O'Dowd, Josh]

>> OK I'll go with your other suggestion.  If I use a BaseContext subclass
> implementation and add it to the tree, I should be able to avoid persisting
> anything from that context in the session, and keep it request-scoped.  For
> that, would I just add it to the PRC?  (Last question... honest!)

> You can add it pretty much anywhere you want within reason, but directly under is the simplest way and is certainly guaranteed to be inviolate for the life of the request.

Well, now I am in a pickle...  My intention was to add a "scratch" context to the tree for the attribute-filter to access in a policy rule script.  I was unaware that the attribute-filter process runs BEFORE the profile actions which identify and run my postAuthenticationFlow interceptor, which does the context tree addition.  Is there a way to re-run the attribute-filter process from the interceptor, or am I left with the only option I see, which is to drill into and manipulate the attribute context from the interceptor, and then just proceed?

Josh