Customers on private tenants with BYOK are not able to log in

What to do

• Check whether you use Mural Authentication, Billing, Learning, Canvas and 7 more. 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 26m it lasted.

  Anything that failed between 2022-05-02 13:58 UTC and 2022-05-02 16:24 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. investigatingMay 2, 2022, 1:58 PM UTC

   Some users are currently unable to sign in to MURAL. We know this is a major service disruption. We're investigating the issue and working to restore regular service as soon as possible. Please check our status page for the most up-to-date info status.mural.co

   provider

2. monitoringMay 2, 2022, 2:17 PM UTC

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

   provider

3. monitoringMay 2, 2022, 3:05 PM UTC

   We are continuing to monitor for any further issues.

   provider

4. resolvedMay 2, 2022, 4:24 PM UTC

   This incident has been resolved

   provider

5. postmortemMay 17, 2022, 4:56 PM UTC

   **What happened?** A small number of customers using BYOK experienced an issue with logging in to the MURAL application. Authentication requests were being redirected from their customer tenants to the main [app.mural.co](http://app.mural.co) tenant, resulting in their users being unable to log in. Initial reports of this were received from MURAL customers on Sunday May 1st. Further reports were received on Monday May 2nd, at which point the issue was classified as a major incident and our task force was engaged. ‌ **Summary** MURAL’s task force started investigating at 13:58 UTC on Monday May 2nd. The cause of the issue was identified as being an incorrect configuration in how users on custom tenants were being routed through the login process. Once the issue was identified, a fix was rolled out at 14:07 UTC. This immediately corrected the login flow for clients using BYOK. ‌ ‌**What we've done to avoid this happening again** Parts of the login flow for BYOK clients had been hard-coded. We have changed this to be dynamically generated, reducing the risk of code-based errors. We are also researching avenues to improve the automated monitoring of login issues.

   provider

Corrections

None so far.

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