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 following software must be installed and operational.
- Security Expert 4.3.344.20 or higher
- Security Expert SOAP 1.6.0.11 or higher
- Configuring Operator for Inlet
- Navigate to Global > Operators.
- Add new operator and fill inn following:
- Name: Username could for example be ( Inlet Soap )
- Username: inlet. Make sure to send this to inlet
- Password: make an password min 8 digit, upper and lowercase and a symbol.
- Role: administrator (or you can make your own role) - Click Save.
- The following information has to be sent to Inlet:
- Security Expert username and password (Operator)
- Details regarding the doors to control (door name and database id, doortype name and database id)
- 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 SOAP API.
- 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: 195.1.208.179 (for debugging and support)
Ports that need to be mapped:
External TCP port 8040 to internal TCP port 8040 on the Server.