Important Changes to Network Requirements for Identity Platform

Follow

In our efforts to provide more reliable services to our customers, SecureAuth is actively migrating legacy services from existing data centers to Amazon Web Services. As part of the migration, new IP addresses must be accessible by your SecureAuth IdP appliance(s). These IP addresses are used for communications between the SecureAuth IdP Appliance(s) and the SecureAuth Cloud Service Endpoints.

 

Below is the list the new IP addresses that need to be accessible by SecureAuth IdP appliance(s) over TCP ports 80 and 443.

 

If your environment includes software firewall(s), physical firewall(s), and / or proxies, please verify that outbound rules are configured to accommodate the URLs and IPs listed below.


us-cloud.secureauth.com & nge-cloud.secureauth.com (v9.3 and below TCP 80 and 443)

75.2.72.232 
99.83.164.204

 

us-trx.secureauth.com (TCP 443)

75.2.50.208
99.83.150.226

 

us-services.secureauth.com (TCP 443)

13.248.146.241
76.223.20.206

 


us-audit.secureauth.com (TCP 443)

75.2.60.253
99.83.226.254

 


sparkles-content.prod.secureauth.com (TCP 443)

13.248.244.218
76.223.113.195

 


ids.secureauth.com (TCP 443)

13.248.159.205
76.223.23.250

 

 

us-polaris.secureauth.com (TCP 443)

15.197.205.255
3.33.245.231


We anticipate that we will complete our migration to Amazon Web Services by September 30th, 2021. Please ensure that IPs whitelisted and are accessible by your SecureAuth IdP Appliance(s) before this date to avoid any service disruption.

 

Once these new IPs are active, it will substantially reduce the number of IPs that need to be whitelisted, making whitelisting much easier moving forward.

 

For more information and a comprehensive list of all IP Addresses required for SecureAuth Cloud Services, please refer to https://docs.secureauth.com/2104/en/secureauth-cloud-services.html

 

1 out of 1 found this helpful

Comments

0 comments

Article is closed for comments.