Invalid signature error when signing in with SSO

What to do

• Check whether you use Mural Authentication, Learning, Website. 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 2h 31m it lasted.

  Anything that failed between 2023-07-14 11:26 UTC and 2023-07-14 13:56 UTC may need a replay.

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

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

Updates from Mural 5

1. investigatingJul 14, 2023, 11:26 AM UTC

   Some users are unable to log in to Mural via SSO, with an error message of “invalid signature”. We are investigating and will restore regular service as soon as possible.

   provider

2. investigatingJul 14, 2023, 12:24 PM UTC

   We are continuing to investigate this issue.

   provider

3. monitoringJul 14, 2023, 12:59 PM UTC

   We've implemented a fix that should resolve the issue. We're monitoring the results to make sure this has the intended effect and will update this message as soon as we've been able to confirm this.

   provider

4. resolvedJul 14, 2023, 1:56 PM UTC

   The fix we implemented earlier has been successful in resolving the issue and full service has been resolved. We apologize for the inconvenience this interruption caused, and will be conducting a full review to avoid a repeat in the future.

   provider

5. postmortemJul 18, 2023, 3:40 PM UTC

   **Summary** On 13th July 2023, we implemented a change to our SAML SSO login flow. This change was released to production at 7pm UTC and we started receiving sporadic reports of login issues that were treated as isolated incidents, as the vast majority of Mural users were able to continue accessing without issues. By 11am UTC on the 14th July, the volume of login issues had increased and we activated our taskforce to investigate the cause. By 11:25 UTC we identified a potential cause of the issue and started preparing a fix. At 11:45 UTC we made the decision to roll back the change from the previous day, which was completed at 12:15 UTC. As of 12:15 UTC login behavior returned to normal parameters.‌ **‌What we've done to avoid this happening again** The change we implemented on Thursday afternoon was rolled back and we are preparing a new change that will avoid impacting the SAML SSO login flow.

   provider

Corrections

None so far.

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