2
|
1 |
#
|
|
2 |
|
|
3 |
# Password file for Remote JMX API authentication. This file defines
|
|
4 |
# the different roles and their passwords.
|
|
5 |
|
|
6 |
# The file format for the password file is syntactically the same as
|
|
7 |
# the Properties file format. The syntax is described in the Javadoc
|
|
8 |
# for java.util.Properties.load.
|
|
9 |
|
|
10 |
# A typical password file has multiple lines, where each line is blank,
|
|
11 |
# a comment (like this one), or a password entry.
|
|
12 |
|
|
13 |
# A password entry consists of a role name and an associated password.
|
|
14 |
# The role name is any string that does not itself contain spaces or
|
|
15 |
# tabs. The password is again any string that does not contain spaces
|
|
16 |
# or tabs. Note that passwords appear in the clear in this file, so it
|
|
17 |
# is a good idea not to use valuable passwords.
|
|
18 |
|
|
19 |
# A given role should have at most one entry in this file. If a role
|
|
20 |
# has no entry, it has no access.
|
|
21 |
# If multiple entries are found for the same role name, then the last
|
|
22 |
# one is used.
|
|
23 |
|
|
24 |
# In a typical installation, this file can be read by anybody on the
|
|
25 |
# local machine, and possibly by people on other machines.
|
|
26 |
# For security, you should either restrict the access to this file,
|
|
27 |
# or specify another, less accessible file in the management config
|
|
28 |
# file as described above.
|
|
29 |
|
|
30 |
# Role and password used for authentication by the RMI connector in
|
|
31 |
# this example.
|
|
32 |
#
|
|
33 |
admin adminPassword
|
|
34 |
user userPassword
|