Application Name | LabLogs.co |
Application Type | Cloud-Based Web Application |
|
|
Required Client Installation | None |
PHI Data | None |
|
|
Internet Connection | Required - High Speed (10Mbps+ Recommended) |
Browser Recommendations | Chrome 60+, Edge 80+, FireFox 51+ |
Device Recommendations | Desktop Workstations, iOS or Android Tablets |
|
|
Application URL | |
Application URL (Dedicated Environments) | |
Authentication Methods | Default: In-App Authentication Optional Integration SSO via SAML, OAuth, Others |
Ad Blockers | Enable for https://app.lablogs.co site. (Ad Blockers for the site limit functionality of support) |
Whitelist Domains | Main Web App wss://*.lablogs.co cognito-idp.us-east-1.amazonaws.com *.amazoncognito.com
Frameworks
Intercom Support App widget.intercom.io api-iam.intercom.io js.intercomcdn.com intercom-sheets.com static.intercomassets.com wss://nexus-websocket-a.intercom.io
Log Rocket |
All domains listed are accessed via outbound connections initiated by the user’s browser when using the LabLogs web application.
In other words:
When a user opens LabLogs, their browser makes secure HTTPS or WSS requests to the required services (LabLogs, authentication, support tools, etc.).
These connections originate from the client’s network and go out to the internet.
There are no inbound connections initiated by those services into the client’s network.
From a firewall perspective, the only requirement is that the client network allows outbound traffic to the domains listed in the article so the browser can load the application and its supporting services correctly.
If those domains are blocked by a firewall or proxy, some parts of the application (authentication, fonts, support widget, logging, etc.) may not load properly.