We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again.
From the evening of April 28 through the early evening of April 29 (UTC), customers using ADP Single Sign-On (SSO) were unable to log in to JazzHR via ADP. Login attempts failed during the OAuth callback step, preventing access through ADP authentication.
In addition to SSO login failures, a smaller set of customers experienced issues with ADP integration features (such as onboarding data pulls and candidate exports) and a limited number of other third‑party integrations that rely on outbound connections.
To minimize disruption, Customer Support temporarily disabled ADP SSO for affected tenants upon request, allowing end users to sign in using direct (non‑SSO) credentials until the issue was resolved.
A configuration change introduced as part of a routine infrastructure update caused the application to unintentionally route outbound traffic through an internal network proxy.
Although the errors surfaced most visibly in ADP SSO login flows, the same underlying issue affected multiple outbound integrations during the same window.
Once identified, the offending configuration change was fully reverted, restoring the previous behavior where outbound requests bypass the internal proxy unless explicitly required.
After the corrected environment was redeployed:
Customer Support then re‑enabled ADP SSO for affected tenants and confirmed restored functionality.
To reduce the likelihood and impact of similar issues in the future, we are implementing the following measures: