This method ensures that in no way an unknown user will be able to display or attempt to hack the system console .
This method is highly recommended when publishing the Artica Web console on the Internet.This feature is available with Artica v4.40, v4.30 SP 206 + HotFix, Artica 4.30 SP 208, Artica 4.30 Service Pack instable 759
¶ Single Authentication
Since the client certificate can be built by administrator, it is possible to allow identification only via the certificate.
The administrator installs his certificate in his browser and connects directly to the web console without having to enter his password and user account. ( see the procedure here )
Of course you can enable both methods (SSL Client certificate checking + Login ).
The client certificate provides SSL identification and the administrator must enter his credentials to access the web console.
¶ Multiple Artica servers authentication.
It is possible to install the server certificate generated on one Artica server to several Artica servers.
In this way, the user will have a single client certificate installed in his browser and will be able to connect to all Artica servers that have the same server certificate installed.
¶ Members authentication
Artica has the ability to manage a user base via its local, LDAP or Active Directory database.
It is possible to generate a certificate for the different members of each database so that your members who have privileges can identify themselves on the Artica Web console.