Not sure if 🐛 or RTFM 👉
# general
s
Not sure if 🐛 or RTFM 👉
1. User registers with Patient Access turned on, 2. Multiple accounts are created 3. User relogs in, sees profile chooser listing
n
of profiles all on same instance
foo-prod
lets say 4. Admin goes and deletes user on
foo-prod
creates and account 5. logs out, logs in 6. Sees account selector with
n+1
profiles listed, non appear to allow the user to login
Question: 1. did I configured something wrong? 2. Am I allowing button mashing -> multiple account creation duet some auth callback issue 3. Why are there ghost profiles if I deleted them? Thank you
r
Hi @stellar4879 , i can try to help! Are you running on our hosted instance, or on a self-hosted server?
Related question - are you using our Sign In / Registration Forms?
s
Hi Rahul, Thank you for the follow-up. 1. Hosted 2. Yes, 3. User had done multiple QA passes, but reports using Google to create the accounts (I had manually deleted the duplicates in the Medplum admin panel) Related but different. A personal email I used for QA shows
Choose Profile
upon attempted login no account exists. However, when registering the app responds with
"text": "User must be scoped to the project"
Logging into the Medplum panel I do not see the user associated with any of our instances. I believe I had deleted this user to tidy up after using the email for initial go round of MP. I am assuming this is a nuance of your identity management I haven't read about fully yet.
r
Sorry for the delay here Ryan - this is my guess at what's happening. There are Medplum "users" (https://www.medplum.com/docs/api/fhir/medplum/user) and project memberships (https://www.medplum.com/docs/api/fhir/medplum/projectmembership). It sounds like one of the accounts is in a state where there is a user but no membership for your account. It's a current limitation that there is no way to re-link as an admin.
To workaround in the short term we recommend making a new account for testing using the + sign in the email.
We are working on the right model to manipulate and expose the memberships. cc: @rahul1
s
No rush; thank you @reshma . I will follow-up in an issue if we develop any salient suggestions.
178 Views