If your network infrastructure applies SSL decryption/inspection, please bypass this rule.
¶ 1-List of required permissions on your infrastructure
¶ Protocole
| Protocole | Port |
|---|---|
| http | 80 |
| https | 443 |
| wss | 443 |
| iicontrol (TCP) | 19527 |
¶ Application (CMS)
| Link | IP Serveur |
|---|---|
| https://www.emity.io | 51.91.236.193 |
| https://link.emity.io | 164.132.50.105 |
| https://eclick.emity.io | 51.75.142.36 |
| https://link.wepub.fr | 164.132.50.105 |
| https://widgets.emity.io | 51.75.142.36 |
| https://media.emity.io | 198.244.190.18 |
| wss://ws.emity.io | 51.75.142.36 |
¶ Iicontrol (For Iiyama TV's)
| Link | IP Serveur |
|---|---|
| - | 34.90.246.68 |
¶ 2-List of optional permissions on your infrastructure
¶ Services
| https://fonts.googleapis.com | https://www.google.com |
| https://maps.google.com | https://embed.waze.com |
| https://sdk.canva.com | https://new.express.adobe.com |
¶ Widgets
| https://embed.waze.com/fr/ | https://monrer.fr/ |
| https://api.openweathermap.org/ | https://lcalendrier.fr |
| https://widget.intramuros.org |
¶ RSS Feed
¶ 3-HTTPS Data Flow :
-
Connection Initiation: When our E-Box application needs to access our secure services, it sends an HTTPS connection request to our servers. This request is usually made via the application's user interface and includes information such as the requested URL and connection parameters.
-
Establishing a Secure Connection: Once the HTTPS connection request is received, our servers establish a secure connection with the E-Box application using the SSL/TLS protocol (Secure Sockets Layer/Transport Layer Security). This ensures that all data exchanged between the E-Box application and our servers is encrypted and protected against unauthorized interception.
-
Data Exchange: Once the secure connection is established, the E-Box application can send secure HTTP requests to our servers to access the desired resources and services. Our servers process these requests, retrieve the necessary data from our secure databases, and return the results to the E-Box application via the established HTTPS connection.
-
Connection Termination: After all data has been exchanged between the E-Box application and our servers, the HTTPS connection can be closed. This may be initiated either by the E-Box application or by our servers, depending on specific protocols and configurations. Closing the connection ensures resource release and system security.
¶ 4-WSS Data Flow:
-
Connection Initiation: To establish a secure WebSocket (WSS) connection with our servers, the E-Box application sends an initial connection request via HTTPS, as described previously. This request also includes an upgrade request to WebSocket.
-
Establishing the WebSocket Connection: Once the upgrade request to WebSocket is accepted by our servers, the connection is established using the secure WebSocket protocol (WSS). This enables real-time, bidirectional communication between the E-Box application and our servers, ideal for applications requiring continuous updates.
-
WebSocket Data Exchange: With the secure WebSocket connection established, the E-Box application and our servers can exchange data bidirectionally and in real time. This includes messages, status updates, real-time notifications, and more. All exchanged data is encrypted to ensure its security and integrity.
-
Connection Termination: When WebSocket communication is no longer needed, the connection can be closed by sending a close message from either the E-Box application or our servers. Once the connection closure is confirmed on both sides, it is terminated, freeing the resources used.
In summary, our HTTPS and WSS data flows ensure secure and efficient communication between our servers and the E-Box application, providing an optimal user experience while maintaining the confidentiality and integrity of the exchanged data.
