You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
The operation will return null as expected but on server side a SecurityException is thrown. This is different from e.g. getTest which will return a response with Content-Length: 0 (and no security exception is thrown on server side) and the status code is HttpStatus.SC_NOT_FOUND.
This is probably happening because AuthorizationServiceBean#isUserAuthorizedForReport can't get the report (because it doesn't exist anymore) and properly check permissions, so it returns false and this results in the SecurityException.
The question is whether we want to give the user information about the existence of the report by returning SC_NOT_FOUND or hide this info by throwing this security exception even if the report doesn't exist.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The operation will return null as expected but on server side a SecurityException is thrown. This is different from e.g. getTest which will return a response with Content-Length: 0 (and no security exception is thrown on server side) and the status code is HttpStatus.SC_NOT_FOUND.
This is probably happening because AuthorizationServiceBean#isUserAuthorizedForReport can't get the report (because it doesn't exist anymore) and properly check permissions, so it returns false and this results in the SecurityException.
The question is whether we want to give the user information about the existence of the report by returning SC_NOT_FOUND or hide this info by throwing this security exception even if the report doesn't exist.
The text was updated successfully, but these errors were encountered: