Statistics
| Revision:

root / tmp / org.txm.setups / shared / win / jre / lib / management / jmxremote.password.template @ 2748

History | View | Annotate | Download (2.8 kB)

1
# ----------------------------------------------------------------------
2
#           Template for jmxremote.password
3
#
4
# o Copy this template to jmxremote.password
5
# o Set the user/password entries in jmxremote.password
6
# o Change the permission of jmxremote.password to read-only
7
#   by the owner.
8
#
9
# See below for the location of jmxremote.password file.
10
# ----------------------------------------------------------------------
11

    
12
##############################################################
13
#        Password File for Remote JMX Monitoring
14
##############################################################
15
#
16
# Password file for Remote JMX API access to monitoring.  This
17
# file defines the different roles and their passwords.  The access
18
# control file (jmxremote.access by default) defines the allowed
19
# access for each role.  To be functional, a role must have an entry
20
# in both the password and the access files.
21
#
22
# Default location of this file is $JRE/lib/management/jmxremote.password
23
# You can specify an alternate location by specifying a property in 
24
# the management config file $JRE/lib/management/management.properties
25
# or by specifying a system property (See that file for details).
26

    
27

    
28
##############################################################
29
#    File permissions of the jmxremote.password file
30
##############################################################
31
#      Since there are cleartext passwords stored in this file,
32
#      this file must be readable by ONLY the owner,
33
#      otherwise the program will exit with an error. 
34
#
35
# The file format for password and access files is syntactically the same
36
# as the Properties file format.  The syntax is described in the Javadoc
37
# for java.util.Properties.load.
38
# Typical password file has multiple  lines, where each line is blank,
39
# a comment (like this one), or a password entry.
40
#
41
#
42
# A password entry consists of a role name and an associated
43
# password.  The role name is any string that does not itself contain
44
# spaces or tabs.  The password is again any string that does not
45
# contain spaces or tabs.  Note that passwords appear in the clear in
46
# this file, so it is a good idea not to use valuable passwords.
47
#
48
# A given role should have at most one entry in this file.  If a role
49
# has no entry, it has no access.
50
# If multiple entries are found for the same role name, then the last one
51
# is used.
52
#
53
# In a typical installation, this file can be read by anybody on the
54
# local machine, and possibly by people on other machines.
55
# For # security, you should either restrict the access to this file,
56
# or specify another, less accessible file in the management config file
57
# as described above.
58
#
59
# Following are two commented-out entries.  The "measureRole" role has
60
# password "QED".  The "controlRole" role has password "R&D".
61
#
62
# monitorRole  QED
63
# controlRole   R&D
64