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:
- Locksmith installs the locks.
- The Xesar software must be installed and operational on version 3.3.13 or higher
- Create a User for Inlet, and add the following permissions:
- Partition Administrator
- IT supplier makes sure we can communicate with HTTPS, either through proxy or domain with HTTPS directly.
- 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.
- Make sure both the firewall on the router and the firewall on the windows machine are set correctly.
- Inlet needs to receive the following to email support@inlet.tech :
- Customer Name
- Public accessible URL or static IP for us to access the server.
- Xesar username
- Xesar password
- Details regarding what doors and/or access level to control
- 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: 77.110.204.178 (for debugging and support)
Ports that need to be mapped:
External TCP port 443 to internal TCP port 443 on the Server.
External TCP port 1883 to internal TCP port 1883 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