Skip to content
OutageDeck

Incident detail

Harness Login Failure in EU1 environment

Resolved incidentMajor1 affected service

Timeline window

to

Outage alerts

Get alerted the next time Harness breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Harness alerts work

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    Harness login is failing. We are investigating the problem.

  2. Monitoring

    A fix has been implemented and we are monitoring the results.

  3. Monitoring

    We are continuing to monitor for any further issues.

  4. Resolved

    This incident has been resolved.

  5. Resolved

    ### Summary

    During a planned security improvement to rotate service authentication secrets in the EU1 environment, an out of sequence secret value was inadvertently applied to a subset of internal services. This resulted in authentication failures between platform components, causing login failures. The issue was resolved by rolling back the token configuration to the previous known-good version and validating service recovery.

    ### Impact

    Affected environment: EU1

    Customer-visible impact: Login Failures

    No customer data was lost or corrupted.

    ### Root Cause

    As part of a planned security initiative, authentication secrets used for communication between internal platform services were rotated in the EU1 .

    During the rotation process, an secret value was inadvertently misconfigured for one of the services. There was a newer format of secret and had to be applied in a certain order. This created a mismatch between services that authenticate using the shared token, causing authentication requests to be rejected with HTTP 400 errors.

    The authentication failures prevented CI components from obtaining log service tokens, disrupted delegate task creation, and prevented log streaming for affected pipeline executions.

    ### Resolution

    Engineering responded by:

    • Reverting the token configuration to the previous known-good secret.
    • Restoring consistent authentication across affected services.

    ### Follow-up Actions

    To reduce the likelihood of similar incidents in the future, Harness will:

    • Implement additional pre-rotation and post-rotation validation checks to verify that the correct secret values and formats are applied before changes are activated.
    • Introduce automated verification of authentication between dependent services immediately following secret rotations.
    • Strengthen operational safeguards and deployment validation for security credential rotation procedures to detect configuration mismatches before they can impact customer workloads.