Suddenly no longer able to log into one of our pro...
# support
y
Hi there, All of a sudden (as of about an hour ago), we're seeing this error message when trying to log into one of our projects using SSO:
Copy code
{
  "resourceType": "OperationOutcome",
  "issue": [
    {
      "severity": "error",
      "code": "invalid",
      "details": {
        "text": "User not found"
      }
    }
  ],
  "extension": [
    {
      "url": "https://medplum.com/fhir/StructureDefinition/tracing",
      "extension": [
        {
          "url": "requestId",
          "valueUuid": "0305b242-53e1-413c-b624-248908b9a8e0"
        },
        {
          "url": "traceId",
          "valueUuid": "ed7faa2b-0d61-4f8c-a8bf-350217f4f4a6"
        }
      ]
    }
  ]
}
Several of us are seeing this issue. Those of us seeing the issue have memberships to multiple projects (namely, our dev and staging projects). We can all log into dev just fine, but staging is suddenly showing us this error. Strangely enough, we just invited a new practitioner to our staging environment (who does not exist in our dev environment), and he is able to log in with no issue. I tried fishing around in the admin UI to see if there was a missing project membership, but alas, our project memberships all seem to be configured correctly.
r
Hi @yaaaaale ! Let me take a look and get back to you ASAP
@yaaaaale , can you DM me the email of the user in question?
@yaaaaale are you trying to log into the Medplum App, or into your app
y
My app
I'm able to log into the Medplum app just fine
Copy code
curl 'https://api.medplum.com/auth/external?code=[redacted]&state=%7b%22projectId%22%3a%22fb0e477b-f07c-4cc6-aba5-e4ead035f347%22%2c%22clientId%22%3a%22e81ba252-ab0b-4135-93ad-d64aea838e57%22%2c%22redirectUri%22%3a%22https%3a%2f%2fcare.stage.imaginepediatrics.tech%22%7d&session_state=44b75c6b-8399-4c02-8e26-91a24aa64882' \
  -H 'authority: api.medplum.com' \
  -H 'accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7' \
  -H 'accept-language: en-US,en;q=0.9' \
  -H 'cookie: _ga=GA1.1.193635368.1691511258; _ga_SHW0ZNT27G=GS1.1.1693739529.71.1.1693739529.0.0.0; medplum-a3df5988-183c-4433-b100-3e29a0157ffc=' \
  -H 'dnt: 1' \
  -H 'referer: https://care.stage.imaginepediatrics.tech/' \
  -H 'sec-ch-ua: "Not_A Brand";v="8", "Chromium";v="120"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "macOS"' \
  -H 'sec-fetch-dest: document' \
  -H 'sec-fetch-mode: navigate' \
  -H 'sec-fetch-site: cross-site' \
  -H 'sec-fetch-user: ?1' \
  -H 'upgrade-insecure-requests: 1' \
  -H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36' \
  --compressed
r
Documenting for the community: - Underlying issue was that some users were invited both as Practitioners and as Patients. This caused them to have two users for the same project, which broke the sign-in flow
@yaaaaale - I just wanted to follow up, after the user cleanup, are things working ok?
y
Yes, they were! We had to do a little more cleanup with project memberships, but in the end all was well
158 Views