Skip to content

Incident detail

SSO login failures for the published Harness Okta application

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Harness breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are currently investigating this issue.

  2. Identified

    The issue has been identified and a fix is being implemented.

  3. Identified

    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.

  4. Identified

    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.

  5. Resolved

    This incident has been resolved.

Keep exploring

More from Harness

Neighboring incidents on Harness's timeline and the rest of their record on OutageDeck.