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 principals for Inlet and the connections to locks here.
Practical and Technical Requirements:
- Locksmith installs the locks.
- The IT supplier provides a server capable of running the ARX software and ensures the server's security with a firewall and access control measures. Details regarding IP addresses and ports that need to be opened in windows and firewall can be found at the end of this document.
- IT supplier installs HTTPS certificates to enable proper HTTPS communication.
- Locksmith makes sure ARX version 3.1.13 or newer is installed on the server and configures the locks and access groups.
- Locksmith enables HTTPS in ARX, and makes sure the URL https://localhost:5003/arx return (Your connection is not private)
- Locksmith ensures that the ARX license includes an import/export module to make the API accessible from the internet.
- Locksmith creates a user for Inlet in ARX, granting necessary rights to control the locks via the API.
- Locksmith sets up a "Manual PIN" card format, which is used to create codes in the locks.
- Locksmith ensures that that the door is set to card only, NOT card + pin.
- IT supplier ensures IP whitelisting and sets up port forwarding from an external port to an internal port on the server, enabling access to the API.
- Inlet needs to receive the following information by mail to support@inlet.tech:
- Customer Name
- Information on what locks and lock groups Inlet should set up.
- ARX username and password
- Name of the card format (Only if code is to be used)
- Number of digits required for that card format (Only if code is to be used)
- Public URL or static IP address of the server.
- Inlet retrieves IDs for the locks to configure Inlet with the locking system.
- Inlet provides information to the main system/booking system for testing.
- Inlet requires a minimum of 2 weeks of testing with the main system/booking system after the installer has completed all the steps above.
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 5003 to internal TCP port 5003 on the Server.
Access System Server IP Address Configuration:
A static IP address should be assigned to prevent it from being changed during a restart, and causing downtime due to the mapping in the previous point