"Security constraints prevent access to requested page"

[sigmachiuta]

I have published a report and added it to a dashboard with the role of "public" but i am still receiving an error "Security constraints prevent access to requested page".   I added the role of ITIL to the report and my test user had ITIL, nogo.. So I started debugging security, first I had a read ACL issue with sys_report, so (for testing) I added the role of public to that ACL.   That cleared the ACL issue but the report still wouldn't show.   I navigated to the table with my test user   foo_bar.list and received the same error.   The security debugger shows all green when navigating to the table how can i debug this security issue when navigating to the table doesnt show me any problems, and why did I need to add public to sys_report?   The plugin "Report Security - enforce access control checks" is enabled and my instance is Fuji.   My gut tells me that its a table ACL but with the debugger not showing me what ACL is not evaluating correctly i am at a loss.

[J_Sukhsagar]

Hello Sigmachiuta,

Making a report public is not always as simple as it seems. On any report there is a button that publishes that report so that it can be viewed publicly. It is also necessary that the records being displayed by the report have a public role or else the report will be empty.

Please follow the below links for better understanding:

Scheduling and Publishing Reports - ServiceNow Wiki

Creating a Public Report - ServiceNow Wiki

Regards,

Sukhsagar

PS: Hit like, Helpful or Correct depending on the impact of the response

[Dale Hynes]

This KB Article explains the underlying change around database views that causes this and provides a solution.

ServiceNow KB: Database View records require read ACLs created for non-admin users after upgrade to ...

[klaytonz]

Ironic, I get this message to the KB articles linked above "You do not have sufficient privileges to access this knowledge item"