Introduction

From VAKA generation 4, there is the option to administer VAKA through an entirely new, intuitive web interface, VAKA Admin*. Initially, functionality for daily system administration is included. For Installer settings and less frequent system configuration, the Java client is used.

VAKA Admin is being constantly developed, and future versions will contain enhanced functionality.

*VAKA Admin is available only in systems with a V60 domain controller.

Certificates

Certificates are installed so that web browsers will not report that the connection between VAKA Admin and the administration computer is insecure.

Certificates are also needed for communication between system components, such as between B60 devices and/or reservation and information panels.

VAKA supports three types of certificates:

VAKA-generated certificate

In this case, B60 generates a local root certificate + web server certificate and distributes these in the system without any intervention required by the administrator.

VAKA-generated root certificates must be installed in the web browser (or system) before it is possible to set up a secure connection.

The advantage of this type of certificate is that a secure connection to the IP address for B60 can be established, as the locally issued certificate is valid for the LAN IP, WAN IP and host name of B60.

Remember: As everyone who connects to the system must install certificates in the web browser, this solution is not suitable for systems that involve reservations over the internet.

Let's Encrypt

Let’s Encrypt is the most convenient option for administrators and users/clients who surf to B60, including reservations made over the internet.

This is a free service that offers devices the opportunity to request and renew certificates automatically.

The services requires port 80 (HTTP) to be open to the connection point so that this is able to accept enquiries from the Let’s Encrypt server. This mechanism is used by Let’s Encrypt to ensure that whoever is requesting a certificate really is the “owner” of the host name.

In practice, this type of root certificate is known to the web browser, meaning that no configuration/installation is required on the web browser (client side).

Customer-specific certificate

If there is already a customer-specific certificate solution, this can also be used for VAKA Admin. For management, refer to the customer’s IT Department.