TigerConnect runs on the Amazon Web Services (AWS) elastic cloud infrastructure. Due to the nature of elastic scaling in response to dynamic throughput needs, the TigerConnect server application may communicate from a range of different IP addresses. Clients with network firewalls in place must proactively allow communications to this range of IP addresses. There are over 10 million public IP addresses contained within the AWS infrastructure. For this reason, TigerConnect strongly discourages the use of an OSI Layer 3 (network) firewall to restrict access via whitelisted IP addresses, as this may unnecessarily open the customer’s infrastructure to a wider attack surface. Rather, we encourage the use of OSI Layer 7 (application) firewall rules to restrict access and only allow HTTPS traffic to the *.tigertext.com, *.tigertext.me, *tigerconnect.com, *.med.tc domains.
Customers may decide to use OSI Layer 3 firewalls, accepting the risk inherent in whitelisting large ranges of IP addresses that may not be used for TigerConnect, including without limitation the risk of allowing access to the customer’s private network by outside parties. The list of current AWS IP addresses may be consumed in JSON format from Amazon. See https://aws.amazon.com/blogs/aws/aws-ip-ranges-json for more information.
NOTE: Append both ‘http://’ or ‘https:// to properly whitelist the below URLs.
NOTE: Similar to whitelisting all AWS IP addresses, it is the customer’s responsibility and risk should they choose to whitelist the entire *.cloudfront.net domain.
The following IP addresses and ports must be allowed for outgoing (egress) traffic from your network:
Include Port: 443
Please ensure the following email addresses are whitelisted to ensure proper delivery of TigerConnect communications:
Aliases and reply-to email addresses for TigerConnect emails:
The following IP address and ports must be allowed for users with LDAP Authentication:
|18.104.22.168||IIS – 443
LDAPS – 636
Note: This is only applicable to those who utilize TigerConnect’s VoIP Audio or Video Calling feature, or our TigerConnect Patient Engagement Patient Video Feature.
If Layer 7 filtering is used whitelist the following URLs:
If Layer 3 filtering is used whitelist the following IP Addresses ranges:
Note: TigerConnect provides support on the below browsers for the following URLs:
Supported Browsers for TigerConnect Clinical Collaboration and TigerConnect Physician Scheduling include:
TigerConnect Web App
Supported browsers include:
Supported desktop and servers:
The TigerConnect Clinical Collaboration Desktop App is available on the systems listed below and includes all the features you need to streamline your workflows.
TigerConnect Desktop App
To download the TigerConnect Desktop Application to your Windows or Mac, Click Here.
Please note: Updates from TigerConnect app versions that are older than the two most recent versions may require users to log back in. TigerConnect Physician Scheduling app releases may require users to log back in.
Note: This is only applicable to those who have opted for Client-Hosted archiving. This does not apply to TigerConnect-Hosted Archiving.