1751 |
set httpd port 2812 |
set httpd port 2812 |
1752 |
allow hauk:monit |
allow hauk:monit |
1753 |
|
|
1754 |
|
Finally it is possible to define some users as read-only users. A |
1755 |
|
read-only user can read the monit web pages but will I<not> get |
1756 |
|
access to any push-buttons and cannot change a service from the |
1757 |
|
web interface. |
1758 |
|
|
1759 |
|
set httpd port 2812 |
1760 |
|
allow admin:password |
1761 |
|
allow hauk:monit read-only |
1762 |
|
|
1763 |
|
A user is set to read-only by using the I<read-only> keyword |
1764 |
|
B<after> username:password. In the above example the user I<hauk> |
1765 |
|
is defined as a read-only user, while the I<admin> user has all |
1766 |
|
access rights. |
1767 |
|
|
1768 |
|
NB! a monit client will use the I<first> username:password pair |
1769 |
|
in an allow list and you should B<not> define the first user as a |
1770 |
|
read-only user. If you do, monit console commands will not work. |
1771 |
|
|
1772 |
If you use Basic Authentication it is a good idea to set the |
If you use Basic Authentication it is a good idea to set the |
1773 |
access permission for the control file (~/.monitrc) to only |
access permission for the control file (~/.monitrc) to only |
1774 |
readable and writable for the user running monit, because the |
readable and writable for the user running monit, because the |