Harness: SSO login failures for the published Harness Okta application

Harness · split.ioImpact: noneidentified2026-09-29 20:57 UTC

Public — what happened

Summary

We identified an issue that applies only to SP-initiated login through the published Harness Okta application. After a recent update to that application, those login attempts returned an HTTP 400 error when the configured SSO URL was missing from Additional ACS URLs. General SAML 2.0 configurations in Okta are not affected. Immediate Solutions: Use IDP-initiated login. Start the login from the Harness application tile in Okta. Or Add your Harness SSO URL to Additional ACS URLs in the published Harness Okta application.

Timeline

Started — 2026-09-29 20:50 UTC
Last update — 2026-09-29 20:57 UTC
Ongoing at last check.

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

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 →

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