The user changed their email, or the user can log in to Labfolder, but all their data is missing

If the authentication is managed by an external identity provider such as Active Directory, then any user available in the identity provider can log in. But, the email is the link to the user’s data. Users who change their email will lose access to all their Labfolder data.

This case is normal when connecting to a new identity provider.

Probably, the same person will have two users in Labfolder database, one with each email. However, the user with the email registered with the new identity provider will not have any data.

The fix is to manually update the user’s email in the database so the email with the data will be the same email from the identity provider.

Follow these steps:

1. Ensure that the user with the missing data has logged in to the application using your current identity provider;

2. Connect to Labfolder database - Platform Customer FAQ | How can I connect to the embedded Labfolder database in Kubernetes;

3. Identify the user with multiple emails with the query:

SELECT id, firstName, lastName, email, iamId FROM labfolder.user ORDER BY firstName;

You need to identify the user based on his name. Notice both emails, the old and new ones, for the same person. The user with the empty iamId is the user with the data (Let’s use old@mail.example). The user with iamId present is the user currently used by the identity provider (Let’s use new@mail.example).

4. Change the email of the user with the iamId to deprecate and remove the iamId:

update labfolder.user 

set email = 'new@mail.example-deprecated', iamId = null 

where email = 'new@mail.example'

5. Change the email of the old user to match the email of the identity provider:

update labfolder.user 

set email = 'new@mail.example'

where email = 'old@mail.example'

6. Ask the user to log in again using the identity provider.