Allowlist requirements for Condeco Screens
If you use allowlists or denylists you must allow access to the fully qualified domains listed below.
Android 8 Screens
| Domain | Protocol / PORT | Fully Qualified Domain Names | Reason / Usage |
|---|---|---|---|
| *.appcenter.ms | HTTPS/443 | in.appcenter.ms | Application Logging |
| *.connectproduction.azure-devices.net | HTTPS/443 | connectproduction.azure-devices.net | IoT messages |
| *.condecoconnect.com | HTTPS/443 | portal.condecoconnect.com | API calls (registration, RFID etc.) |
| *.condecoconnect.com | HTTPS/443 | storage.condecoconnect.com | Config data and firmware versions |
| *.condecoconnect.com | HTTPS/443 | services.condecoconnect.com | Connection test endpoint |
| Appropriate calendar service URL | HTTPS/443 |
NTP Service
By default, screens are configured to use the standard NTP services listed below, however, screens can be configured to use a custom NTP service. At least one of the NTP servers must be added to the allowlist.
| NTP Service | NTP server | Protocol / PORT | Reason / Usage |
|---|---|---|---|
| Android | time.android.com | NTP/123 (UDP only) | |
| Apple | time.apple.com | NTP/123 (UDP only) | |
| time.google.com | NTP/123 (UDP only) | ||
| Android | 2.android.pool.ntp.org | NTP/123 (UDP only) | |
| Time.Local | time.local | NTP/123 (UDP only) | time.local is included to allow a customer to stand up their own internal NTP server if required |
| Custom NTP | NTP/123 (UDP only) | Screen settings allow a custom NTP server to be set. |
Condeco Screens Admin Portal
login.microsoftonline.com
portal.condecoconnect.com
cdn.linearicons.com
cdnjs.cloudflare.com
fonts.googleapis.com
widget.uservoice.com
connectblobstorage.blob.core.windows.net
by2.uservoice.com
az416426.vo.msecnd.net
fonts.gstatic.com
dc.services.visualstudio.com
*.condecoconnect.com
Emails
*.ct.sendgrid.net
westeurope.azureedge.net
Mobile API
connectpasswordless.azurewebsites.net
https://westeurope.condecoconnect.com
Post your comment on this topic.