Live  /  Harness  /  Incident

Harness: SSO login failures for the published Harness Okta application

Harness · split.ioResolved2026-10-02 00:33 UTC
Public — what happened

Summary

Harness said some customers signing in through its published Okta application ran into login failures, starting around 20:50 UTC on 2026-09-29. According to Harness, the problem affected only logins begun from the Harness side rather than from Okta, and it appeared after a recent change to that Okta application, producing an error when the customer's SSO address was not listed among the application's additional allowed return addresses. The company said other standard Okta single sign-on setups were not affected, and it suggested starting the login from the Harness tile in Okta or adding the SSO address to that list as workarounds. Harness marked the incident resolved on 2026-10-02 at 00:33.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Harness against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Harness: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Harness report →

More from Harness

Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.

The full archive is on the Harness status & history page.

Related: Harness status & history. SquidGrid is not affiliated with Harness.