1 ############################################################## 2 # Password File for Remote JMX Monitoring 3 ############################################################## 4 # 5 # Password file for Remote JMX API access to monitoring. This 6 # file defines the different roles and their passwords. The access 7 # control file (jmxremote.access by default) defines the allowed 8 # access for each role. To be functional, a role must have an entry 9 # in both the password and the access files. 10 # 11 # Default location of this file is $JRE/lib/management/jmxremote.password 12 # You can specify an alternate location by specifying a property in 13 # the management config file $JRE/lib/management/management.properties 14 # or by specifying a system property (See that file for details). 15 16 17 ############################################################## 18 # File permissions of the jmxremote.password file 19 ############################################################## 20 # Since there are cleartext passwords stored in this file, 21 # this file must be readable by ONLY the owner, 22 # otherwise the program will exit with an error. 23 # 24 # The file format for password and access files is syntactically the same 25 # as the Properties file format. The syntax is described in the Javadoc 26 # for java.util.Properties.load. 27 # Typical password file has multiple lines, where each line is blank, 28 # a comment (like this one), or a password entry. 29 # 30 # 31 # A password entry consists of a role name and an associated 32 # password. The role name is any string that does not itself contain 33 # spaces or tabs. The password is again any string that does not 34 # contain spaces or tabs. Note that passwords appear in the clear in 35 # this file, so it is a good idea not to use valuable passwords. 36 # 37 # A given role should have at most one entry in this file. If a role 38 # has no entry, it has no access. 39 # If multiple entries are found for the same role name, then the last one 40 # is used. 41 # 42 # In a typical installation, this file can be read by anybody on the 43 # local machine, and possibly by people on other machines. 44 # For # security, you should either restrict the access to this file, 45 # or specify another, less accessible file in the management config file 46 # as described above. 47 # 48 # Following are two commented-out entries. The "measureRole" role has 49 # password "QED". The "controlRole" role has password "R&D". 50 # 51 # monitorRole QED 52 # controlRole R&D 53 54 guest guestpasswd 55 admin adminpasswd 56
