Administrator's Guide - Kerio Software Archive

12.2 User authentication at the web interface
Figure 12.3
Creating a new “self-signed” certificate for Kerio Control’s web interface
issued by a trustworthy certification authority. However, they can install the certificate in the
browser without worrying since they are aware of who and why created the certificate. Secure
communication is then ensured for them and no warning will be displayed again because your
certificate has all it needs.
Another option is to purchase a full certificate from a public certification authority (e.g.
Verisign, Thawte, SecureSign, SecureNet, Microsoft Authenticode, etc.).
To import a certificate, open the certificate file (*.crt) and the file including the corresponding
private key (*.key). These files are stored in sslcert under the Kerio Control’s installation
directory.
The process of certification is quite complex and requires a certain expertise. For detailed
instructions contact Kerio technical support.
12.2 User authentication at the web interface
User authentication is required for access to the Kerio Control’s web interface. Any user with
their own account in Kerio Control can authenticate to the web interface. Depending on the
right to view statistics (see chapter 16.2), either Kerio StaR is opened or a page with status
information and personal preferences is displayed upon logon.
If more than one Active Directory domain are used (see chapter 16.4), the following rules apply
to the user name:
• Local user account — the name must be specified without the domain (e.g. admin),
• Primary domain — missing domain is acceptable in the name specification (e.g.
jsmith), but it is also possible to include the domain (e.g. jsmith@company.com),
• Other domains — the name specified must include the domain
(e.g. drdolittle@usoffice.company.com).
167