Issue 43278- display forbidden exception message in error handling page #2472
Conversation
|
@labkey-adam I couldn't find the server side callers to LoadLibraryAction and LogClientExceptionAction. The ones I found were client side and the caller to those actions doesn't pass the container. |
There was a problem hiding this comment.
A key change mentioned in the issue is to remove the @IgnoresForbiddenProjectCheck annotation on both actions. And test. I had to add the annotation was because these actions were getting called in a specific folder/project instead of root. Since you've made no changes to the callers I suspect they're still NOT root-based URLs.
|
Actually, hold on... let me pull this down locally. Something is strange with the isForbiddenProject handling. |
|
Sorry, @labkey-ankurj , I was mistaken. Turns out the "forbidden project" check was NOT failing originally because the invocation was to a different project. It forbid an admin impersonating in a project from accessing root, which is arguably too strict, but that's what's it's doing. Let's forget about removing the annotation... your code is good! But I'd like to make my follow-on change to this branch... I'll let you know when my change is ready. |
Rationale
Display forbidden exception message in error page instead of the general permission exception message.
Related Pull Requests