As part of iPipeline's ongoing investment in improving the performance, scalability, reliability, and security of its authentication services, the Ping Identity infrastructure is being migrated to AWS. This migration introduces new network endpoints that may require updates to customer firewall, allowlist, proxy, WAF, and other network security configurations.
Customers who restrict access using IP allowlists or other network security controls should review and update their configurations before the deadline below.
Important: New AWS IP addresses must be added, not used to replace existing Ping Identity IP addresses. Existing approved Ping Identity IP addresses must remain in place until iPipeline provides formal notice that they can be removed.
Key Date: September 1, 2026 – Deadline for customers to complete required network and allowlist updates. This is a customer readiness date and not the production migration date. Migration schedules will be communicated separately
This change may impact applications and integrations that rely on Ping authentication, including:
iGO® Illustrations (excluding WELiS®) Resonant® DocFast® Quote (LifePipe and iSolve®) FormsPipe AdminPipe iService Content Suite Single Sign-On (SSO) integrations PingFederate and PingAccess-protected services Carrier and vendor integrations using Ping authentication services.
Technical Details: The complete list of current and new IP addresses, implementation guidance, FAQs, and supporting documentation can be found on the iPipeline Customer Portal:
If you have questions regarding this update, please contact your iPipeline Account Representative.
Posted Jul 23, 2026 - 17:29 EDT
This scheduled maintenance affects: DocFast, FormsPipe, iGO, iGO Client Collaboration, Illustrations, Quote, Portals and Tools, Resonant, XRAE, and iGO Evolve.