While investigating that issue, we found that it was caused by changes we made to enhance security in the product. That resulted in our "Won't Fix" designation.
We decided instead that we needed to provide some type of workaround, and we have been testing various options in order to make a recommendation. The last internal update to that issue was a week ago, so I asked the team to publicly summarize their findings.
See the related conversation on ALF-21521.
Thanks for your patience. (And thank you for pinging me on this thread jpotts.)