Skip to content

Add note about scripting permissions [DOC-734] [v/5.4] #2256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mscwilson merged 1 commit into from
Jul 22, 2026
Merged

Add note about scripting permissions [DOC-734] [v/5.4] #2256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/modules/maintain-cluster/pages/monitoring.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,6 +91,11 @@ Management Center allows you to execute scripts that can automate interactions w

By default, scripting is disabled for security. Scripting engines give code access to the underlying system on the members (files and other resources) and run with the same permissions as the current user. You can enable scripting in the member configuration file:

[IMPORTANT]
====
When scripting is enabled, it grants full, unrestricted access to the cluster and is *not* limited by the permissions assigned to individual Management Center users. Enable it with caution, especially in production, and consider leaving it disabled if granular access control is critical. See the xref:{page-latest-supported-mc}@management-center:tools:scripting.adoc[Management Center scripting documentation] for details.
====

[tabs]
====
XML::
Expand Down Expand Up @@ -122,6 +127,11 @@ Note that the https://jcp.org/en/jsr/detail?id=223[JSR 223^] API is used in Haze

Management Center allows you to execute client operations using built-in Hazelcast Command-Line Client (CLC) in the user interface. This console is useful for testing and development purposes. You can enable the console in the member configuration file:

[IMPORTANT]
====
When the console is enabled, it grants full access to the cluster through the Command-Line Client and is *not* limited by the permissions assigned to individual Management Center users. Enable it with caution, especially in production, and consider leaving it disabled if granular access control is critical.
====

[tabs]
====
XML::
Expand Down
Loading