0N/A# Access control file for Remote JMX API access to MBeanServer resources.
0N/A# This file defines the allowed access for different roles.
0N/A# The file format for the access file is syntactically the same as the
0N/A# Properties file format. The syntax is described in the Javadoc for
0N/A# A typical access file has multiple lines, where each line is blank,
0N/A# a comment (like this one), or an access control entry.
0N/A# An access control entry consists of a role name, and an associated access
0N/A# level. The role name is any string that does not itself contain spaces or
0N/A# tabs. It corresponds to an entry in the password file. The access level
0N/A# is one of the following:
0N/A# "readonly" grants access to read attributes of MBeans.
0N/A# For monitoring, this means that a remote client in this
0N/A# role can read measurements but cannot perform any action
0N/A# that changes the environment of the running program.
0N/A# "readwrite" grants access to read and write attributes of MBeans, to
0N/A# invoke operations on them, and to create or remove them.
0N/A# This access should be only granted to trusted clients,
0N/A# since they can potentially interfere with the smooth
0N/A# operation of a running program.
0N/A# A given role should have at most one entry in this file. If a role has no
0N/A# entry, it has no access.
0N/A# If multiple entries are found for the same role name, then the last access
0N/A# Access rights granted to the authenticated identity by the RMI connector