Background:
Because there are many components in motion, we've compiled a list outlining requirements, clarifications, and areas of responsibility to ensure the seamless integration between Inlet and the lock system.
Read more about the security principles for Inlet and the connections to locks here.
Practical and Technical Requirements:
-
The locksmith installs the locks, installs Tidomat on the server, and configures the locks in Tidomat.
-
The locksmith ensures that Tidomat has version cd ver 10.1 installed.
-
You can find the version number under installed program.
-
-
The version of the Booking API must be at least 1.7.
-
The booking version can be retrieved from http://localhost:8899/booking/version?api_key=12345
-
-
We want to connect with HTTPS, so a proxy/netscaler or similar must be created to achieve a secure connection.
-
The locksmith must create an API key, which is done by adding or retrieving an existing API key in the file: C:\Program Files (x86)\Tidomat\TIDOMAT PW32\php\script\private\pw32api\api_key_admin.txt
-
Allowed IP addresses must also be added to:
-
C:\Program Files (x86)\Tidomat\TIDOMAT PW32\php\script\private\pw32api\allowedIPs.php
-
-
The IT provider delivers a server where the Tidomat server can be installed and secures the server with a firewall and access control, as well as installs an SSL certificate for secure connection.
-
The IT provider ensures to whitelist IP addresses and set up port forwarding from the external port to the internal port on the server so that we can access the API.
-
The IT provider opens the firewall on the Windows machine where Tidomat is installed so that traffic from Inlet is not blocked anywhere along the way.
-
The IT provider can then access the public IP on port 8899 and should be able to connect directly to the Tidomat server.
-
Inlet needs receive the following to email support@inlet.tech:
- Customer Name
- Information on what locks and lock groups Inlet should set up.
- Tidomat API key
- Public IP, or a proxy address that responds to HTTPS.
-
Inlet retrieves the locks to configure Inlet with the locking system.
-
Inlet provides information to the top system/booking system that they can test.
-
Inlet requires at least 2 weeks of testing with the top system/booking system after the installer has completed the above points.
IP addresses that need to be whitelisted:
Required: 52.164.185.179
Optional: 79.160.124.141 (for debugging and support)
Ports that need to be mapped:
External TCP port 8899 to internal TCP port 8899 on the Server.