SAML Login Failures

What to do

• Check whether you use Asana in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2025-04-08 22:47 UTC and 2025-04-08 22:47 UTC may need a replay.

• Subscribe to Asana's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=asana works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Asana 2

1. resolvedApr 8, 2025, 10:47 PM UTC

   From April 4th to April 8th, approximately 0.5% of users using SAML for authentication experienced errors during login.

   provider

2. postmortemApr 16, 2025, 10:47 PM UTC

   **Incident:** From April 4 to April 8, 2025, a subset of users were blocked from logging in with SAML, despite no changes to their identity provider setup. We believe the root cause to be a combination of recent code changes upgrading our infrastructure. These changes inadvertently affected how SAML responses were processed. **Impact:** Approximately 0.5% of users who authenticate through SAML were unable to log in to their Asana accounts during this period. No customer data was lost or compromised, and users who do not use SAML were unaffected. Our Customer Support team worked with affected domains to restore access while we resolved the issue. **Moving forward:** Our existing monitors did not trigger for this incident, which led to an extended period of downtime. We are improving existing monitoring and increasing monitor coverage to allow us to detect and respond to authentication issues more quickly in the future. Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.