TeamDynamix IP Addresses

TeamDynamix Work Management

The TeamDynamix Work Management solution uses a number of IP Addresses and Domains to provide service. Oftentimes our customers will choose to specifically allow our resources to ensure proper delivery of service to their users. You can find a list of resources to trust at one of the links below:

The following items are typically considered when a customer is developing a allow list/block list strategy.

  1. TeamDynamix Web Applications (TDNext, TDClient, TDWebApi, etc.)
    1. Web traffic received by TeamDynamix as a result of normal web application use.
  2. LDAP Authentication
    1. LDAP authentication requests coming from TeamDynamix as a result of choosing and configuring the LDAP authentication option.
  3. Email Monitors
    1. IMAP requests coming from TeamDynamix as a result of TeamDynamix Email Monitor configurations.
  4. Workflow Web Service Calls
    1. HTTP requests coming from TeamDynamix as a result of a Ticketing Workflow Web Service Step.
  5. Bomgar Integration
    1. HTTP requests coming from TeamDynamix as a result of Bomgar Integration configuration.
  6. RSS Feeds
    1. HTTP requests coming from TeamDynamix as a result of RSS Feed configuration.
  7. Outbound Email
    1. For sending mail through a custom SMTP setup (not the TeamDynamix out-of-the-box mail). These will be mail messages coming from TeamDynamix, for notifications and other purposes sent through a client-specific server or mail service. Typically on-premise or external mail sending systems need to allow access by a range of IPs to send on behalf of TeamDynamix.
    2. For receiving mail in user mailboxes, we recommend allowing outbound email based on the domain. If this is not an option for your organization and you choose to allow outbound email using IP Addresses instead, please refer to Amazon Simple Email Service Documentation for a list of IP Addresses that are used.

TeamDynamix iPaaS

The TeamDynamix iPaaS solution uses a number of IP Addresses and Domains to provide service. Oftentimes our customers will choose to specifically allow our resources to ensure proper delivery of service to their users. You can find a list of resources to trust at one of the links below:

The following items are typically considered when a customer is developing a allow list/block list strategy.

  1. iPaaS Web Application
    1. Web traffic received by TeamDynamix as a result of normal web application use.
  2. iPaaS Proxy
    1. Polling mode
      1. HTTP traffic received by TeamDynamix as part of the communication between the proxy and the iPaaS Web Application.
      2. HTTP traffic received by Azure blob storage as part of the communication between the proxy and the iPaaS Web Application.
    2. Direct / Callback mode
      1. HTTP requests coming from TeamDynamix to the proxy server.
      2. HTTP traffic received by TeamDynamix as part of the communication between the proxy and the iPaaS Web Application.
      3. HTTP traffic received by Azure blob storage as part of the communication between the proxy and the iPaaS Web Application.
  3. Flow Execution
    1. HTTP and other requests coming from TeamDynamix as a result of iPaaS flow execution.
  4. Outbound Email
    1. For receiving mail in user mailboxes, we recommend allowing outbound email based on the domain. At this time TeamDynamix utilizes a 3rd-party for outbound email which does not provided a dedicated list of IP addresses for adding to an allow list.

Changes as of 01/12/2022

Updated this article to distinguish the differences between TeamDynamix Work Management and TeamDynamix iPaaS

Changes as of 12/14/2018

We are adding several new IP Addresses and specifically removing the IP Address 104.45.129.97. We are now specifying trusted resources at the following location: https://app-eus.teamdynamix.com/meta

This change is being made as part of infrastructure improvements to our environment.

75% helpful - 4 reviews

Details

Article ID: 6725
Created
Wed 6/10/15 11:39 AM
Modified
Wed 1/12/22 4:09 PM