Parallels Plesk Panel - 9.5 - Unix Administrator’s Guide
Parallels® Plesk Panel
Copyright Notice
ISBN: N/A
Parallels
660 SW 39th Street
Suite 205
Renton, Washington 98057
USA
Phone: +1 (425) 282 6400
Fax: +1 (425) 282 6444
© Copyright 1999-2010,
Parallels, Inc.
All rights reserved
Distribution of this work or derivative of this work in any form is prohibited unless prior written
permission is obtained from the copyright holder.
Patented technology protected by U.S.Patents 7,328,225; 7,325,017; 7,293,033; 7,099,948;
7,076,633.
Patents pending in the U.S.
Product and service names mentioned herein are the trademarks of their respective owners.
Contents
Preface 6
Typographical Conventions ........................................................................................................... 6
Feedback ....................................................................................................................................... 7
Administering Security Settings 8
Configuring Firewall ....................................................................................................................... 9
Configuring SELinux Policy for Your Parallels Plesk Panel Server ............................................ 10
Securing the /tmp Partition .......................................................................................................... 11
Achieving Compliance with Payment Card Industry Data Security Standard 12
Using Event Tracking Mechanism 18
Adding Event Handlers ................................................................................................................ 19
Removing Event Handlers ........................................................................................................... 20
Event Parameters Passed by Event Handlers ............................................................................ 21
Session (Login) Settings Event ......................................................................................... 23
Desktop Preset Event ....................................................................................................... 23
Client Account Event ......................................................................................................... 24
Client Status Event ............................................................................................................ 24
Disk Space Limit Event for Client ...................................................................................... 25
Traffic Usage Limit Event for Client................................................................................... 25
Client Limits Event ............................................................................................................ 25
Client Permissions Event .................................................................................................. 26
Client Preferences Event .................................................................................................. 29
Client‟s GUID Event .......................................................................................................... 29
Clients Template Event ..................................................................................................... 30
Client‟s IP Pool Event ........................................................................................................ 30
Client‟s Site Application Package Event ........................................................................... 30
Domain Event .................................................................................................................... 31
Domain Limits Event ......................................................................................................... 31
Domain Status Event ........................................................................................................ 32
Domain‟s GUID Event ....................................................................................................... 32
Domains Template Event .................................................................................................. 33
DNS Zone Event for Domain ............................................................................................. 33
Disk Space Limit Event for Domain................................................................................... 33
Traffic Usage Limit Event for Domain ............................................................................... 33
Domain Owner Change Event .......................................................................................... 34
Subdomain Event .............................................................................................................. 34
Domain Alias Event ........................................................................................................... 35
Domain Alias, DNS Zone Event ........................................................................................ 35
Physical Hosting Event ..................................................................................................... 36
Mail Account Event ........................................................................................................... 38
Web User Event ................................................................................................................ 39
Mailing List Event .............................................................................................................. 39
Parallels Plesk Panel User Event...................................................................................... 40
Domain Administrator Account Event ............................................................................... 40
Domain Administrator‟s Permissions Event ...................................................................... 41
Preface 4
Site Application Event ....................................................................................................... 43
Service Event .................................................................................................................... 44
IP Address Event .............................................................................................................. 44
Forwarding Event .............................................................................................................. 45
Administrator Information Event ........................................................................................ 45
Database Server Event ..................................................................................................... 46
Parallels Plesk Panel Component Event .......................................................................... 46
Database Event ................................................................................................................. 46
Database User Account Event .......................................................................................... 47
License Key Event ............................................................................................................ 47
Reseller Account Event ..................................................................................................... 47
Reseller Status Event ........................................................................................................ 48
Disk Space Limit Event for Reseller .................................................................................. 48
Traffic Usage Limit Event for Reseller .............................................................................. 49
Reseller Limits Event ........................................................................................................ 49
Reseller Permissions Event .............................................................................................. 50
Reseller Preferences Event .............................................................................................. 53
Reseller‟s GUID Event ...................................................................................................... 53
Resellers Template Event ................................................................................................. 54
Reseller‟s IP Pool Event .................................................................................................... 54
Reseller‟s Site Application Package Event ....................................................................... 54
Configuring Apache Server 55
Getting Familiar with Virtual Host Structure and Permissions .................................................... 56
Enabling Piped Logs for Web Server to Reduce the Risk of Web Service Disruption ................ 58
Recompiling Apache With More File Descriptors ........................................................................ 59
Recompiling Apache With More File Descriptors on RedHat-like System........................ 60
Recompiling Apache With More File Descriptors on Debian System ............................... 62
Recompiling Apache With More File Descriptors on FreeBSD System............................ 63
Including Directives into Web Server Configuration File ............................................................. 65
Customizing httpd.include for Domains ....................................................................................... 66
Preventing Graphics Hotlinking on a Web Site ........................................................................... 66
Apache Port Change ................................................................................................................... 67
Example of Web Server Configuration File ....................................................................... 69
Example of Domain Configuration File ............................................................................. 70
Example of Subdomain Configuration File ........................................................................ 72
Example of Webmail Configuration File ............................................................................ 74
Example of Mailman Configuration File ............................................................................ 75
Configuring Sitebuilder for Work With Changed Apache Port .......................................... 76
Changing Tomcat Java Connector Ports 78
Configuring Mail 79
Configuring a Mailing List Where Only Members are Allowed to Post to .................................... 80
Importing a List of E-mail Addresses into a Mailing List .............................................................. 80
Limiting the Number of Recipients of a Mail Message ................................................................ 81
Training SpamAssassin for All Mail Accounts on the Server ...................................................... 82
Limiting the Maximum Number of Child Processes for spamd ................................................... 83
Fighting Against Spam on Qmail Mail Server ............................................................................. 84
Restoring Mail Configuration ....................................................................................................... 86
Installing Custom SSL Certificates for Qmail or Courier-IMAP Mail Servers .............................. 87
Installing SSL Certificate for Qmail ................................................................................... 88
Installing SSL Certificates for Courier-IMAP Mail Server .................................................. 90
Preface 5
Installing Adobe ColdFusion 91
Using Open Relay Option for Your Mail Server 94
Configuring APS Applications Catalog 95
Checking Free Disk Space Before Starting the Backup Process 97
6 Preface
In this section:
Typographical Conventions ............................................................................... 6
Feedback .......................................................................................................... 7
Formatting convention
Type of Information
Example
Special Bold
Items you must select, such as
menu options, command
buttons, or items in a list.
Go to the QoS tab.
Titles of chapters, sections,
and subsections.
Read the Basic Administration
chapter.
Italics
Used to emphasize the
importance of a point, to
introduce a term or to
designate a command line
placeholder, which is to be
replaced with a real name or
value.
The system supports the so
called wildcard character
search.
Monospace
The names of style sheet
selectors, files and directories,
and CSS fragments.
The license file is called
license.key.
Preface
Typographical Conventions
The following kinds of formatting in the text identify special information.
Preface 7
Preformatted Bold
What you type, contrasted with
on-screen computer output.
Unix/Linux:
# cd /root/rpms/php
Windows:
>cd %myfolder%
Preformatted
On-screen computer output in
your command-line sessions;
source code in XML, C++, or
other programming languages.
Unix/Linux:
# ls –al /files
total 14470
Windows:
>ping localhost
Reply from 127.0.0.1:
bytes=32 time<1ms
TTL=128
Feedback
If you have found an error in this guide, or if you have suggestions or ideas on how to
improve this guide, please send your feedback using the online form at
http://www.parallels.com/en/support/usersdoc/. Please include in your report the guide‟s title,
chapter and section titles, and the fragment of text in which you have found an error.
In this chapter:
Configuring Firewall ........................................................................................... 9
Configuring SELinux Policy for Your Parallels Plesk Panel Server .................... 10
Securing the /tmp Partition ................................................................................ 11
C H A P T E R 1
Administering Security Settings
Administering Security Settings 9
Configuring Firewall
Make sure these ports are opened for all Parallels Plesk Panel services to work with a
firewall:
20 for ftp-data;
21 for ftp;
22 for ssh;
25 for smtp;
53 for dns (TCP and UDP);
80 for http (web server and Parallels Plesk Panel updater);
106 for poppassd (for localhost only);
110 for pop3;
113 for auth;
143 for imap;
443 for https;
465 for smtps;
587 for mail message submission;
990 for ftps;
993 for imaps;
995 for pop3s;
3306 for mysql;
5224 for (outgoing connections only) plesk-license-update;
5432 for postgres;
8443 for plesk-https;
8880 for plesk-http;
9080 for tomcat;
5224 for license updates.
10 Administering Security Settings
Configuring SELinux Policy for Your
Parallels Plesk Panel Server
To configure SELinux you need to know the rules that should be added into the system
policy. SELinux reports all denied messages into the /var/log/audit/audit.log
file and these messages can be easily converted into the rules using the
/usr/bin/audit2allow utility.
cat /var/log/messages | /usr/bin/audit2allow
Also, /var/log/messages.* files can be examined for the SELinux deny messages.
To configure SELinux policy:
1. Add the rules into the appropriate domain file which describes the
application.
For example:
/etc/selinux/targeted/src/policy/domains/program/apache.te
allow httpd_sys_script_t var_t:file { execute getattr };
allow httpd_t self:tcp_socket connect;
allow httpd_t usr_t:dir write;
allow httpd_t var_log_t:file { append getattr setattr };
allow httpd_sys_script_t devlog_t:sock_file write;
allow httpd_sys_script_t self:unix_dgram_socket { connect create write
};
allow httpd_sys_script_t ld_so_cache_t:file execute;
allow httpd_sys_script_t syslogd_t:unix_dgram_socket sendto;
allow httpd_sys_script_t var_t:dir { add_name remove_name write };
allow httpd_sys_script_t var_t:fifo_file write;
allow httpd_sys_script_t var_t:file { create execute_no_trans link
read unlink write };
/etc/selinux/targeted/src/policy/domains/program/named.te
allow named_t named_zone_t:chr_file read;
allow ndc_t named_zone_t:file { getattr read write };
allow named_t named_zone_t:dir { add_name write read remove_name };
allow named_t named_zone_t:file { create unlink write };
/etc/selinux/targeted/src/policy/domains/program/syslogd.te
allow syslogd_t usr_t:file append;
allow syslogd_t usr_t:file ioctl;
2. Perform the following command line to apply changes:
make -C /etc/selinux/targeted/src/policy reload
Administering Security Settings 11
Securing the /tmp Partition
It is recommended to create /tmp as separate partition and mount it with the noexec
and nosuid options.
The noexec option disables the executable file attribute within an entire file
system, effectively preventing any files within that file system from being executed.
The nosuid option disables the SUID file-attribute within an entire file system. This
prevents SUID attacks on, say, the /tmp file system.
To secure the /tmp partition of your Parallels Plesk Panel server:
If /tmp is a separate partition on the server, you only need to edit /etc/fstab
and add the noexec and nosuid options for /tmp. Then remount the partition.
If the /tmp directory resides on the / partition:
a. Create a new partition for /tmp, for example with size 512 MB:
# mkdir /filesystems
# dd if=/dev/zero of=/filesystems/tmp_fs seek=512 count=512
bs=1M
# mkfs.ext3 /filesystems/tmp_fs
b. Add the string into /etc/fstab:
/filesystems/tmp_fs /tmp ext3 noexec,nosuid,loop 1 1
c. Move current /tmp directory content to another location.
d. Mount new /tmpp partition:
# mount /tmp
e. Move content from old /tmp directory to the new one.
To reduce the risk of compromising sensitive data hosted on your server, you might
Option
Description
-- enable all | --disable all
The option “—enable all” switches off weak SSL ciphers
and protocols for Web and e-mail servers.
The option “—disable all” reverts all changes made by the
utility and restores original configuration files, thereby
allowing weak SSL ciphers and protocols for connections to
Web and e-mail servers.
-- enable courier | --disable
courier
Switches off or switches on weak SSL ciphers and
protocols for connections to Courier IMAP mail server.
-- enable apache | --disable
apache
Switches off or switches on weak SSL ciphers and
protocols for connections to the Apache Web server that
serves users‟ sites.
-- enable panel | --disable panel
Switches off or switches on weak SSL ciphers and
protocols for connections to Parallels Plesk Panel.
C H A P T E R 2
Achieving Compliance with Payment
Card Industry Data Security Standard
want to implement special security measures that comply with the Payment Card
Industry Data Security Standard (PCI DSS). The standard is intended to help
organizations protect customer account data. For detailed information about the
standard, refer to
https://www.pcisecuritystandards.org/security_standards/pci_dss.shtml.
This chapter describes the steps required to achieve PCI compliance on Linux and
FreeBSD-based systems.
You first need to run the PCI Compliance Resolver utility available from the Plesk
Control Panel installation directory. It will disable weak SSL ciphers and protocols for
Web and e-mail servers operated by Plesk Control Panel.
To run the utility:
1. Log in to the server shell.
2. Issue the following command:
/usr/local/psa/admin/bin/pci_compliance_resolver—enable all
The following table describes all options supported by the utility.
Achieving Compliance with Payment Card Industry Data Security Standard 13
Some PCI compliance scanners may require that the medium strength SSL ciphers for
access to the Panel be also switched off. For this reason, after you have run the utility,
you need to modify a configuration file that was created by it.
1. Open for editing the file
/usr/local/psa/admin/conf/cipher.lst.
2. Remove all lines from the file.
3. Insert the following line:
ADH-AES256-SHA DHE-RSA-AES256-SHA DHE-DSS-AES256-SHA AES256-SHA KRB5DES-CBC3-MD5 KRB5-DES-CBC3-SHA EDH-RSA-DES-CBC3-SHA EDH-DSS-DES-CBC3SHA DES-CBC3-SHA ADH-DES-CBC3-SHA DES-CBC3-MD5
4. Save the file.
5. Restart the Web server:
On Linux systems, issue the command /etc/init.d/sw-cp-server
restart.
On FreeBSD systems, issue the command /usr/local/etc/rc.d/sw-cp-
server restart.
Now you need to switch off weak SSL ciphers for connections to Qmail or Postfix email server, if you use any of them.
If you use Qmail mail server, issue the following commands at the prompt:
On Linux systems:
echo ‗ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!SSLv2:RC4+RSA:+HIGH:+MEDIUM‘ >
/var/qmail/control/tlsserverciphers
echo ‗ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!SSLv2:RC4+RSA:+HIGH:+MEDIUM‘ >
/var/qmail/control/tlsclientciphers
On FreeBSD systems:
echo ‗ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!SSLv2:RC4+RSA:+HIGH:+MEDIUM‘ >
/usr/local/psa/qmail/control/tlsserverciphers
echo ‗ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:!SSLv2:RC4+RSA:+HIGH:+MEDIUM‘ >
/usr/local/psa/qmail/control/tlsclientciphers
If you use Postfix mail server, modify configuration files:
1. On Linux systems, open for editing the file /etc/postfix/main.cf.
2. On FreeBSD systems, open for editing the file
/usr/local/etc/postfix/main.cf.
3. Add the following lines to the file:
smtpd_tls_protocols = SSLv3, TLSv1
smtpd_tls_ciphers = medium
smtpd_tls_exclude_ciphers = aNULL
smtpd_sasl_security_options = noplaintext
4. Save the file.
5. Restart the mail server:
14 Achieving Compliance with Payment Card Industry Data Security Standard
On Linux systems, issue the command /etc/init.d/postfix restart.
On FreeBSD systems, issue the command /usr/local/etc/rc.d/postfix
restart.
You also need to prohibit access to MySQL database server from external addresses.
To do this, in a firewall that protects your Panel-managed server, add or enable a rule
that prohibits TCP and UDP connections to the port 3306 from all addresses except
127.0.0.1.
To use the firewall that comes with your Parallels Plesk Panel for Linux:
1. Log in to the Panel as administrator.
2. If you did not install the firewall component, install it:
a. Go to Home > Updates (in the Help & Support group).
b. Click the link corresponding to your version of the Panel.
c. Locate Plesk Firewall module, select the corresponding check box,
and click Install.
3. Configure the firewall rule that blocks external MySQL connections and
switch the firewall on:
a. Click the Settings link in the navigation pane.
b. Click Manage Firewall Rules, and then Edit Firewall Configuration.
c. Click the MySQL server link.
d. Select the Deny option and click OK.
e. Click Activate to apply the configuration, and then click Activate
again to switch on the firewall.
To conceal the version of DNS server from potential attackers, do the
following:
1. Open for editing the DNS server‟s configuration file named.conf. On
Linux systems, it is located in /etc/, and on FreeBSD systems, in
/etc/namedb/.
2. Locate the options {} section, and add the version “none” line
there.
3. Restart the named service:
On Deb package-based systems, issue the command /etc/init.d/bind9
restart
On RPM package-based systems, issue the command /etc/init.d/named
restart
On FreeBSD systems, issue the command /etc/rc.d/named restart
Achieving Compliance with Payment Card Industry Data Security Standard 15
To conceal the version of the Apache Web server from potential attackers,
do the following:
1. Open for editing the Web server‟s configuration file.
On Debian, Ubuntu, and SuSE Linux, it is located at
/etc/apache2/apache2.conf.
On other distributions of Linux, it is located at
/etc/httpd/conf/httpd.conf.
On FreeBSD, it is located at /usr/local/etc/apache2/httpd.conf.
2. Add the following lines:
ServerTokens ProductOnly
TraceEnable OFF
3. Save the file.
4. Restart the Web server.
On Deb package-based systems, issue the command /etc/init.d/apache2
restart
On RPM package-based systems, issue the command /etc/init.d/httpd
restart
On FreeBSD systems, issue the command /usr/local/etc/rc.d/apache2
restart
If you have Single Sign-On v.2.2 components installed, then you need to
disable SSL v.2 and weak SSL ciphers for the single sign-on service:
1. Open for editing the file /etc/sw-cp-
server/applications.d/sso-cpserver.conf.
2. Locate the two lines ssl.engine = “enable”.
3. After each of these lines, add the following:
ssl.cipher-list = ―ADH-AES256-SHA:DHE-RSA-AES256-SHA:DHE-DSS-AES256SHA:AES256-SHA:ADH-AES128-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES128SHA:AES128-SHA:KRB5-DES-CBC3-MD5:KRB5-DES-CBC3-SHA:ADH-DES-CBC3SHA:EDH-RSA-DES-CBC3-SHA:EDH-DSS-DES-CBC3-SHA:DES-CBC3-SHA:DES-CBC3MD5:DHE-DSS-RC4-SHA:KRB5-RC4-MD5:KRB5-RC4-SHA:ADH-RC4-MD5:RC4-SHA:RC4MD5:RC2-CBC-MD5:RC4-MD5‖
ssl.use-sslv2 = ―disable‖
4. Save the file.
5. Restart the service:
On Linux systems, issue the command /etc/init.d/sw-cp-server
restart.
On FreeBSD systems, issue the command /usr/local/etc/rc.d/sw-cp-
server restart.
16 Achieving Compliance with Payment Card Industry Data Security Standard
To conceal the version of PHP installed on the server:
1. Create a file with name php.ini in the following directory
On Linux systems, /etc/sw-cp-server/
On FreeBSD systems, /usr/local/etc/sw-cp-server/
2. Add to this file the line expose_php = Off.
3. Save the file.
4. Open for editing the following file:
On Linux systems, /etc/sw-cp-server/applications.d/sso-
cpserver.conf.
On FreeBSD systems, /usr/local/etc/sw-cp-
server/applications.d/sso-cpserver.conf.
5. Locate the following line:
On Linux systems, var.intertpreter = “/usr/bin/sw-engine-cgi”.
On a FreeBSD system, var.intertpreter = “/usr/local/bin/sw-
engine-cgi”.
6. Replace it with the following line:
On Linux systems, var.intertpreter = “/usr/bin/sw-engine-cgi -c
/etc/sw-cp-server/php.ini”.
On a FreeBSD system, var.intertpreter = “/usr/local/bin/sw-
engine-cgi -c /usr/local/etc/sw-cp-server/php.ini”.
7. Save the file.
8. Restart the Web server:
On Linux systems, issue the command /etc/init.d/sw-cp-server
restart.
On FreeBSD systems, issue the command /usr/local/etc/rc.d/sw-cp-
server restart.
To alleviate security risks arising from disclosure of information about files and their
properties by Apache Web server, configure the FileETag directive in the Web server
configuration file.
To do this:
1. Open for editing the Web server‟s configuration file.
On Debian, Ubuntu, and SuSE Linux, it is located at
/etc/apache2/apache2.conf.
On other distributions of Linux, it is located at
/etc/httpd/conf/httpd.conf.
On FreeBSD, it is located at /usr/local/etc/apache2/httpd.conf.
Achieving Compliance with Payment Card Industry Data Security Standard 17
2. Locate the line FileETag INode MTime Size and remove the
INode keyword from this line.
3. Save the file.
4. Restart the Web server.
On Deb package-based systems, issue the command /etc/init.d/apache2
restart
On RPM package-based systems, issue the command /etc/init.d/httpd
restart
On FreeBSD systems, issue the command /usr/local/etc/rc.d/apache2
restart
The Event Manager is designed to help you organize data interchange between
In this chapter:
Adding Event Handlers ...................................................................................... 19
Removing Event Handlers ................................................................................. 20
Event Parameters Passed by Event Handlers ................................................... 21
C H A P T E R 3
Using Event Tracking Mechanism
Parallels Plesk Panel and external systems. It works the following way: you create a
script to be executed upon a certain Parallels Plesk Panel event, and then create an
event handler that triggers the event processing. You can assign several handlers to a
single event.
Important: The Parallels Plesk Panel administrator can create the event handlers that
will trigger scripts running on the server on behalf of the root user. If you wish to restrict
usage of the root account, create an empty file with name
root.event_handler.lock in the location
/plesk_installation_directory/var/.
Using Event Tracking Mechanism 19
Adding Event Handlers
Let‟s, for example, create an event handler for the „client account creation‟ event. The
handler will accept a client name and the client‟s login from environment variables. For
simplicity we will use a shell-script called test-handler.sh that looks as follows:
#!/bin/bash
echo “--------------“ >> /tmp/event_handler.log
/bin/date >> /tmp/event_handler.log # information on
the event date and time
/usr/bin/id >> /tmp/event_handler.log # information on
the user, on behalf of which the script was executed (to ensure
control)
echo “client created” >> /tmp/event_handler.log # information on
the created client account
echo “name: ${NEW_CONTACT_NAME}” >> /tmp/event_handler.log #
client‟s name
echo “login: ${NEW_LOGIN_NAME}” >> /tmp/event_handler.log #
client‟s login
echo “--------------“ >> /tmp/event_handler.log
This script prints some information to a file so that we could control its execution (we
cannot output information to stdout/stderr, as the script is executed in the background
mode).
Suppose, that our script is located in the directory
/plesk_installation_directory/bin (for instance). Let‟s register it by creating
an event handler via Parallels Plesk Panel.
To add an event handler via Parallels Plesk Panel:
1. Go to Home > Event Manager.
2. Click Add New Event Handler. The event handler setup page appears.
3. Select the event, you wish to assign a handler to in the Event menu.
4. Select the priority for handler execution, or specify a custom value. To
do this, select custom in the Priority menu and type in the value.
When assigning several handlers to a single event you can specify the handler
execution sequence, setting different priorities (higher value corresponds to a
higher priority).
20 Using Event Tracking Mechanism
5. Select the system user, on behalf of which the handler will be executed
(“root” user, for example).
6. In the Command input field, specify a command to be executed upon the
selected event. In our example it is /usr/local/psa/bin/test-
handler.sh.
7. Click OK.
Note: In the script, we have specified the variables $NEW_CONTACT_NAME and
$NEW_LOGIN_NAME. During execution of the handler, they will be replaced with
name and login of the created client respectively. The entire list of available variables is
provided in the following section. You should keep in mind that with the removal
operations, the variables of type $NEW_xxx are not set. And with creation operations
the parameters of type $OLD_xxx are not set.
Now if you login to your Parallels Plesk Panel and create a new client, specifying the
value „Some Client‟ in the Contact name field, and „some_client‟ in the field Login, the
handler will be invoked, and the following records will be added to the
/tmp/event_handler.log:
Fri Mar 16 15:57:25 NOVT 2007
uid=0(root) gid=0(root) groups=0(root)
client created
name: Some client
login: some_client
The parameter templates that can be used when setting up an event handler are
presented in the Event Parameters Passed by Event Handlers (see page 21) section.
Removing Event Handlers
To remove an event handler:
1. Go to Server > Event Manager.
2. Select the corresponding check boxes in the list of handlers and click
Remove Selected.
Using Event Tracking Mechanism 21
Event Parameters Passed by Event
Handlers
22 Using Event Tracking Mechanism
In this section:
Session (Login) Settings Event.......................................................................... 23
Desktop Preset Event ........................................................................................ 23
Client Account Event ......................................................................................... 24
Client Status Event ............................................................................................ 24
Disk Space Limit Event for Client ...................................................................... 25
Traffic Usage Limit Event for Client ................................................................... 25
Client Limits Event............................................................................................. 25
Client Permissions Event................................................................................... 26
Client Preferences Event ................................................................................... 29
Client‟s GUID Event .......................................................................................... 29
Clients Template Event ..................................................................................... 30
Client‟s IP Pool Event ........................................................................................ 30
Client‟s Site Application Package Event ............................................................ 30
Domain Event .................................................................................................... 31
Domain Limits Event ......................................................................................... 31
Domain Status Event ......................................................................................... 32
Domain‟s GUID Event ....................................................................................... 32
Domains Template Event .................................................................................. 33
DNS Zone Event for Domain ............................................................................. 33
Disk Space Limit Event for Domain ................................................................... 33
Traffic Usage Limit Event for Domain ................................................................ 33
Domain Owner Change Event ........................................................................... 34
Subdomain Event .............................................................................................. 34
Domain Alias Event ........................................................................................... 35
Domain Alias, DNS Zone Event......................................................................... 35
Physical Hosting Event ...................................................................................... 36
Mail Account Event............................................................................................ 38
Web User Event ................................................................................................ 39
Mailing List Event .............................................................................................. 39
Parallels Plesk Panel User Event ...................................................................... 40
Domain Administrator Account Event ................................................................ 40
Domain Administrator‟s Permissions Event ....................................................... 41
Site Application Event ....................................................................................... 43
Service Event .................................................................................................... 44
IP Address Event .............................................................................................. 44
Forwarding Event .............................................................................................. 45
Administrator Information Event ........................................................................ 45
Database Server Event ..................................................................................... 46
Parallels Plesk Panel Component Event ........................................................... 46
Database Event ................................................................................................. 46
Database User Account Event .......................................................................... 47
License Key Event............................................................................................. 47
Reseller Account Event ..................................................................................... 47
Reseller Status Event ........................................................................................ 48
Disk Space Limit Event for Reseller .................................................................. 48
Traffic Usage Limit Event for Reseller ............................................................... 49
Reseller Limits Event ......................................................................................... 49
Reseller Permissions Event ............................................................................... 50
Reseller Preferences Event ............................................................................... 53
Reseller‟s GUID Event ...................................................................................... 53
Resellers Template Event ................................................................................. 54
Reseller‟s IP Pool Event .................................................................................... 54
Reseller‟s Site Application Package Event ........................................................ 54
Using Event Tracking Mechanism 23
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the event „Session (login) settings changed‟
Allowed
period of
inactivity for
all Parallels
Plesk Panel
users
OLD_SESSION_IDLE_TI
ME
NEW_SESSION_IDLE_TIME
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the events „Desktop preset created, modified, deleted‟
Unique
identification
number of a
desktop
preset
OLD_DESKTOP_PRESET_I
D
NEW_DESKTOP_PRESET_I
D
Type of
desktop
preset
(default
preset for
administrator‟
s desktop,
client‟s
desktop,
domain
administrator‟
s desktop, or
a user‟s
custom
preset)
OLD_DESKTOP_PRESET_T
YPE
NEW_DESKTOP_PRESET_T
YPE
Desktop
preset name
OLD_DESKTOP_PRESET_N
AME
NEW_DESKTOP_PRESET_N
AME
Session (Login) Settings Event
Desktop Preset Event
24 Using Event Tracking Mechanism
Client Account Event
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the events „Client account created‟, „Client account updated‟, „Client account removed‟
Login name
OLD_LOGIN_NAME
NEW_LOGIN_NAME
Required
Contact
name
OLD_CONTACT_NAME
NEW_CONTACT_NAME
Required
Password
OLD_PASSWORD
NEW_PASSWORD
Company
name
OLD_COMPANY_NAME
NEW_COMPANY_NAME
Phone
OLD_PHONE
NEW_PHONE
Fax
OLD_FAX
NEW_FAX
E- mail
OLD_EMAIL
NEW_EMAIL
Address
OLD_ADDRESS
NEW_ADDRESS
City
OLD_CITY
NEW_CITY
State/provinc
e
OLD_STATE_PROVINCE
NEW_STATE_PROVINCE
Postal/zip
code
OLD_POSTAL_ZIP_CODE
NEW_POSTAL_ZIP_CODE
Country
OLD_COUNTRY
NEW_COUNTRY
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the events „Client status updated‟
Contact
name
OLD_CONTACT_NAME
NEW_CONTACT_NAME
Required
Login name
OLD_LOGIN_NAME
NEW_LOGIN_NAME
Required
Status
OLD_STATUS
NEW_STATUS
Client Status Event
Using Event Tracking Mechanism 25
Disk Space Limit Event for Client
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the event „Limit on disk space was reached for the client account‟
Contact
name
OLD_CONTACT_NAME
NEW_CONTACT_NAME
Required
Disk space
limit
OLD_MAXIMUM_DISK_SP
ACE
NEW_MAXIMUM_DISK_SPAC
E
Required
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the events „Limit on traffic usage was reached for the client account‟
Contact
name
OLD_CONTACT_NAME
NEW_CONTACT_NAME
Required
Traffic limit
OLD_MAXIMUM_TRAFFIC
NEW_MAXIMUM_TRAFFIC
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the event „Client limits changed‟
Contact
name
OLD_CONTACT_NAME
NEW_CONTACT_NAME
Required
Maximum
number of
domains
OLD_MAXIMUM_DOMAINS
NEW_MAXIMUM_DOMAINS
Maximum
amount of
disk space
OLD_MAXIMUM_DISK_SP
ACE
NEW_MAXIMUM_DISK_SPAC
E
Maximum
amount of
traffic
OLD_MAXIMUM_TRAFFIC
NEW_MAXIMUM_TRAFFIC
Traffic Usage Limit Event for Client
Client Limits Event
26 Using Event Tracking Mechanism
Maximum
number of
Web users
OLD_MAXIMUM_WEBUSER
S
NEW_MAXIMUM_WEBUSERS
Maximum
number of
databases
OLD_MAXIMUM_DATABAS
ES
NEW_MAXIMUM_DATABASES
Maximum
number of
mailboxes
OLD_MAXIMUM_MAILBOX
ES
NEW_MAXIMUM_MAILBOXES
Mailbox
quota
OLD_MAXIMUM_MAILBOX
_QUOTA
NEW_MAXIMUM_MAILBOX_Q
UOTA
Maximum
number of
mail redirects
OLD_MAXIMUM_MAIL_RE
DIRECTS
NEW_MAXIMUM_MAIL_REDI
RECTS
Maximum
number of
mail groups
OLD_MAXIMUM_MAIL_GR
OUPS
NEW_MAXIMUM_MAIL_GROU
PS
Maximum
number of
mail
autorespond
ers
OLD_MAXIMUM_MAIL_AU
TORESPONDERS
NEW_MAXIMUM_MAIL_AUTO
RESPONDERS
Maximum
number of
mailing lists
OLD_MAXIMUM_MAIL_LI
STS
NEW_MAXIMUM_MAIL_LIST
S
Maximum
number of
Java
applications
OLD_MAXIMUM_TOMCAT_
WEB_APPLICATIONS
NEW_MAXIMUM_TOMCAT_WE
B_APPLICATIONS
Account
expiration
date
OLD_EXPIRATION_DATE
NEW_EXPIRATION_DATE
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the event “Client‟s permissions changed”
Login name
OLD_LOGIN_NAME
NEW_LOGIN_NAME
Permission
to use the
Parallels
Plesk Panel
OLD_CP_ACCESS
NEW_CP_ACCESS
Client Permissions Event
Using Event Tracking Mechanism 27
Permission
to manage
Web site
hosting
account
OLD_PHYSICAL_HOSTIN
G_MANAGEMENT
NEW_PHYSICAL_HOSTING_
MANAGEMENT
Permission
to switch
PHP_safe
mode off and
on
OLD_PHP_SAFE_MODE_M
ANAGEMENT
NEW_PHP_SAFE_MODE_MAN
AGEMENT
Permission
to assign
hard quotas
on disk
space
OLD_HARD_DISK_QUOTA
_ASSIGNMENT
NEW_HARD_DISK_QUOTA_A
SSIGNMENT
Permission
to manage
subdomains
OLD_SUBDOMAINS_MANA
GEMENT
NEW_SUBDOMAINS_MANAGE
MENT
Permission
to manage
domain
aliases
OLD_DOMAIN_ALIASES_
MANAGEMENT
NEW_DOMAIN_ALIASES_MA
NAGEMENT
Permission
to change
the resource
allotments for
the user‟s
Web sites
OLD_LIMITS_ADJUSTME
NT
NEW_LIMITS_ADJUSTMENT
Permission
to manage
DNS zones
for domains
OLD_DNS_ZONE_MANAGE
MENT
NEW_DNS_ZONE_MANAGEME
NT
Permission
to adjust log
recycling
OLD_LOG_ROTATION_MA
NAGEMENT
NEW_LOG_ROTATION_MANA
GEMENT
Permission
to schedule
tasks and
automate
execution of
scripts
OLD_CRONTAB_MANAGEM
ENT
NEW_CRONTAB_MANAGEMEN
T
Permission
to manage
anonymous
FTP service
OLD_ANONYMOUS_FTP_M
ANAGEMENT
NEW_ANONYMOUS_FTP_MAN
AGEMENT
Permission
to manage
Java Web
applications
and Java
Web service
OLD_WEB_APPLICATION
S_MANAGEMENT
NEW_WEB_APPLICATIONS_
MANAGEMENT
28 Using Event Tracking Mechanism
Permission
to manage
Web
statistics
(switch
between
statistics
programs)
OLD_WEB_STATISTICS_
MANAGEMENT
NEW_WEB_STATISTICS_MA
NAGEMENT
Permission
to manage
access to the
server shell
over SSH
OLD_SYSTEM_ACCESS_M
ANAGEMENT
NEW_SYSTEM_ACCESS_MAN
AGEMENT
Permission
to manage
access to the
server shell
in chrooted
environments
over SSH
OLD_NON_CHROOTED_SH
ELL_MANAGEMENT
NEW_NON_CHROOTED_SHEL
L_MANAGEMENT
Permission
to manage
mailing lists
OLD_MAILING_LISTS_M
ANAGEMENT
NEW_MAILING_LISTS_MAN
AGEMENT
Permission
to back up
and restore
data through
the Parallels
Plesk Panel
and use the
backup
repository on
the server
OLD_BACKUP_RESTORE_
FUNCTIONS_USE_LOCAL
_REPOSITORY
NEW_BACKUP_RESTORE_FU
NCTIONS_USE_LOCAL_REP
OSITORY
Permission
to back up
and restore
data through
the Parallels
Plesk Panel
and use
backup
repositories
on thirdparty FTP
servers
OLD_BACKUP_RESTORE_
FUNCTIONS_USE_FTP_R
EPOSITORY
NEW_BACKUP_RESTORE_FU
NCTIONS_USE_FTP_REPOS
ITORY
Permission
to use the
XML API for
Web site
management
OLD_ABILITY_TO_USE_
REMOTE_XML_INTERFAC
E
NEW_ABILITY_TO_USE_RE
MOTE_XML_INTERFACE
Permission
to use the
Desktop
interface
OLD_ABILITY_TO_USE_
DASHBOARD_INTERFACE
NEW_ABILITY_TO_USE_DA
SHBOARD_INTERFACE
Using Event Tracking Mechanism 29
Permission
to use the
standard
Parallels
Plesk Panel
interface
OLD_ABILITY_TO_USE_
STANDARD_INTERFACE
NEW_ABILITY_TO_USE_ST
ANDARD_INTERFACE
Permission
to customize
Desktop
OLD_ABILITY_TO_MANA
GE_DASHBOARD
NEW_ABILITY_TO_MANAGE
_DASHBOARD
Permission
to manage
spam filtering
settings
OLD_ABILITY_TO_MANA
GE_SPAMFILTER
NEW_ABILITY_TO_MANAGE
_SPAMFILTER
Permission
to manage
antivirus
settings
OLD_ABILITY_TO_MAN
AGE_VIRUSFILTER
NEW_ABILITY_TO_MANA
GE_VIRUSFILTER
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the events „Client preferences updated‟
Contact
name
OLD_CONTACT_NAME
NEW_CONTACT_NAME
Required
Login name
OLD_LOGIN_NAME
NEW_LOGIN_NAME
Required
Page size
OLD_LINES_PER_PAGE
NEW_LINES_PER_PAGE
Interface skin
OLD_INTERFACE_SKIN
NEW_INTERFACE_SKIN
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the „Client‟s GUID updated‟ event
Globally
unique
identifier
(GUID)
OLD_GUID
NEW_GUID
Required
Client Preferences Event
Client‟s GUID Event
30 Using Event Tracking Mechanism
Clients Template Event
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the „Template for clients created‟, „Template for clients updated‟, „Template for clients
removed‟ events
Reseller
template ID
OLD_TEMPLATE_ID
NEW_TEMPLATE_ID
Required
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the event „Client‟s IP pool changed‟
Contact
name
OLD_CONTACT_NAME
NEW_CONTACT_NAME
Required
IP address
OLD_IP_ADDRESS
NEW_IP_ADDRESS
Required
Status
OLD_STATUS
NEW_STATUS
Parameter
name and
description
Environment variable name
Notes
Previously used value
New value
For the events „Site application package added to client‟s pool‟, „Site application package
removed from client‟s pool‟
Login name
OLD_LOGIN_NAME
NEW_LOGIN_NAME
Package
name
OLD_PACKAGE_NAME
NEW_PACKAGE_NAME
Client‟s IP Pool Event
Client‟s Site Application Package Event
Loading...