iManager authenticates a user by looking in the ~/etc/passwd
file. Hence, any user with a valid Virtual
Private Servers User Account can access iManager
with their login and password. Access will be granted only to the
user's home directory. If you have configured a user account for
Subhost customers, then they can access iManager
using the Virtual Private Servers hostname, like this:
The users would simply use their user account login
and password in order to authenticate. It is also possible to configure
your Virtual Private Servers so that a user can also access iManager
using their own domain name, like this:
or something more generic like 'mail' instead of
'imanager', for example:
To use either one of the above urls, you would
add one of the following
Alias directives to your web
server configuration file (~/www/conf/httpd.conf).
Alias /imanager/ /usr/local/etc/httpd/htdocs/imanager/
Alias /mail/ /usr/local/etc/httpd/htdocs/imanager/
Of course, you can choose any alias name that
strikes your fancy. You would simply need to replace '/imanager/' or '/mail/' in
one of the previous
Alias directives to be whatever you wish.
An alternative way to configure your Virtual Private
Servers so that a subhosted domain name can access iManager is to
use a canonical domain name such as 'imanager' or 'mail'. Consider
the following examples:
To enable access to iManager in this way,
complete the following steps.
Order a CNAME record in the zone
file for the Virtual Subhost's domain name. There is a
fee for creating custom CNames. We suggest using imanager or mail
for the CNAME record (for example, imanager.SUBHOST-DOMAIN.NAME
but you can specify any name you want.
Add the following
directive to your web server configuration file (~/www/conf/httpd.conf).
NOTE: If you would
like to use a different canonical name, then substitute
the CNAME record you created for
mail above in the
ServerName directives. Do not change