Setup guide – Dormakaba Exos

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:

1. dormakaba exos is installed and fully commissioned in the usual manner by the installer. The integration requires a minimum exos version of 4.2.3.
2. The IT supplier provides a server capable of installing the Exos 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.
3. The IT provider ensures that the exos API can be accessed from a public URL, either an IP address, a proxy, or another domain with SSL.
   
   1. https://NN.NN.NN.NN/ExosAuth/swagger/index.html
   2. https://some.domain/ExosAuth/swagger/index.html
4. The IT provider ensures SSL certificates for a secure connection.
5. The locksmith activates API access.
6. Remember to change the Registration unit to '90 02 with Badge Input' in exos.
7. Follow the manual “rm-kabaexos9300-web-applications-r423-202212-en.pdf”
   Section: 4.1.4.1 Access
   
8. Create an API user via System Management and User Management. These are login details that must be sent to Inlet.
9. Inlet needs receive the following to email support@inlet.tech:
   
   • Customer Name
   • Information on what locks and lock groups Inlet should set up.
   • API username and password
   • Public IP Address and port where we can access the exos API
10. Inlet retrieves IDs from the locks to configure Inlet with the locking system.
11. Inlet provides information to the main system/booking system for testing.
12. 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 443 to internal TCP port 443 on the Server.