Kerio Tech 6 11.2 User authentication at the web interface

Chapter 11 Web Interface

146

Verisign,Thawte,SecureSign,SecureNet,Microsoft Authenticode, etc.).

To import a certiﬁcate, open the certiﬁcate ﬁle (*.crt) and the ﬁle including the correspond-

ing private key (*.key). These ﬁles are stored in sslcert under the WinRoute’s installation

directory.

The process of certiﬁcation is quite complex and requires a certain expertise. For detailed

instructions contact Kerio technical support.

11.2 User authentication at the web interface

User authentication is required for access to the WinRoute’s web interface. Any user with their

own account in WinRoute can authenticate to the web interface. Depending on the right to

view statistics (see chapter 15.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 15.4), the following rules apply

to the user name:

•Local user account — the name must be speciﬁed without the domain (e.g. admin),

•Primary domain — missing domain is acceptable in the name speciﬁcation (e.g.

jsmith), but it is also possible to include the domain (e.g. jsmith@company.com),

•Other domains — the name speciﬁed must include the domain

(e.g. drdolittle@usoffice.company.com).

If none or just one Active Directory domain is mapped, all users can authenticate by their

usernames without the domain speciﬁed.

Note: Authentication at the web interface is a basic user authentication method at the ﬁrewall.

Other authentication methods are described in chapter 10.1.