I was confused by what turned out to be a cache population side effect of client-side message (notification) resolution. I'd realized the importance of removing widgets with side effects from the home page before impersonating, but I hadn't realized that HRSPortlet caches would populate anyway thanks to side effect of resolving the statements resourceURL to audience filter a notification.
Having had the insight that messages can now have these cache population side effects, added documentation to reflect.
Contributor License Agreement adherence:
[x] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.
I was confused by what turned out to be a cache population side effect of client-side message (notification) resolution. I'd realized the importance of removing widgets with side effects from the home page before impersonating, but I hadn't realized that
HRSPortletcaches would populate anyway thanks to side effect of resolving the statementsresourceURLto audience filter a notification.Having had the insight that messages can now have these cache population side effects, added documentation to reflect.
Contributor License Agreement adherence: