Legacy Knowledge Base
Published Sep. 10, 2025

"Someone may be trying to circumvent the permission checker" errors shown in the logs

Written By

Lucas Mesquita

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The following message is identified in the logs:
May 10 11:28:27.159 build-3348 liferay[liferay-64c4b97d99-nvp2x] [dxp] ERROR [http-nio2-8080-exec-18][IncludeTag:128] Current URL /group/guest/~/control_panel/manage?p_p_id=com_liferay_document_library_web_portlet_DLAdminPortlet&p_p_lifecycle=0&p_p_state=maximized&p_v_l_s_g_id=39115&p_p_auth=PVRkZV4k generates exception: java.lang.IllegalArgumentException: Someone may be trying to circumvent the permission checker: {companyId=39077, name=com.liferay.document.library.kernel.model.DLFileEntry, primKey=263212, scope=4}

Environment

  • Liferay DXP 7.0+

Resolution

Additional Information

NOTE: Be sure to take a backup of your database prior to making any changes. Always test the changes in a lower environment before making changes in production.

Making manual changes to the database is not recommended, and should be carefully assessed based on your own business needs and risk factors. Any such operation is performed at the sole discretion of your own team.

Did this article resolve your issue ?

Legacy Knowledge Base