Legacy Knowledge Base
Published Sep. 10, 2025

How to disable Scripting Console

Written By

Adam Zsolnay

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

  • Even if Scripting Console is restricted to those with the server administration role, we would like to disable this scripting functionality in our 7.0 portal.

Environment

  • DXP 7.0

Resolution

  • Scripting from Scripting Console can be disabled by blacklisting the following modules:
    com.liferay.portal.scripting.executor-x.y.z.jar
    com.liferay.portal.scripting.groovy-x.y.z.jar

  • by adding the following values in the blacklistBundleSymbolicNames property in
    com.liferay.portal.bundle.blacklist.internal.BundleBlacklistConfiguration.config (/osgi/configs folder):

    blacklistBundleSymbolicNames=["com.liferay.portal.scripting.executor","com.liferay.portal.scripting.groovy"]

    Expected results: even if this will not remove the Scripting Console itself, scripts cannot be executed from Scripting Console.

    Important note 1: Scripting API should not be disabled, as disabling it seems to break the Script page entirely. Disabling the mentioned 2 modules will not break the core functionality of the portal.

    Important note 2: Please test this configuration in a test environment thoroughly first, before moving these changes to Production.

Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base