Lifecycle Manager uses a set of sync servers to connect to your integrations. If a system you connect to Lifecycle Manager only accepts traffic from approved IP addresses, you must add these sync servers to its allowlist. Otherwise, the integration can't connect. Our Partner Support team can give you the hostname and IP addresses to use.
| Note: This article does not contain the Lifecycle Manager hostname or IP addresses for allowlisting, only instructions on how to contact our Support team to obtain them. |
When you need to allowlist Lifecycle Manager
Add Lifecycle Manager's sync servers to your allowlist if you use either of these:
- An on-premises firewall that restricts access to a server Lifecycle Manager syncs with.
- A SaaS application that restricts API access by IP address.
IP Allowlisting explained
IP allowlisting is a commonly used security feature that allows you to determine exactly who can access specific resources. With allowlisting, you create a list of approved IP addresses, and only those addresses (or ranges) can access your resources.
Lifecycle Manager IP Allowlist
Our Partner Support team will provide you with the Lifecycle Manager hostname that resolves multiple IP addresses currently in use by our sync servers.
We recommend that you use the hostname for your firewall or SaaS application entries rather than individual IP addresses, and not override the DNS TTL using a locally enforced cache duration. All traffic from our sync servers uses port 443.
If it is not possible to allowlist using a hostname, you can get our list of sync server IP addresses by running this command in Windows Command Prompt or macOS/Linux Terminal:
nslookup <hostname>
Where <hostname> is the hostname Partner Support provides to you.
Note: The IP addresses behind the hostname can change without notice. If you allowlisted individual IP addresses and an integration that was working stops connecting, run the nslookup command again and update your allowlist with the current IP addresses. |
