User authentication at the web interface, 2 user authentication at the web interface – Kerio Tech KERIO WINROUTE FIREWALL 6 User Manual
Page 146
Chapter 11
Web Interface
146
Verisign, Thawte, SecureSign, SecureNet, Microsoft Authenticode, etc.).
To import a certificate, open the certificate file (*.crt) and the file including the correspond-
ing private key (*.key). These files are stored in sslcert under the WinRoute’s installation
directory.
The process of certification 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
), 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
), 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. [email protected]),
•
Other domains — the name specified must include the domain
(e.g. [email protected]).
If none or just one Active Directory domain is mapped, all users can authenticate by their
usernames without the domain specified.
Note: Authentication at the web interface is a basic user authentication method at the firewall.
Other authentication methods are described in chapter
.