Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDP: Consider scenarios where 3DR data is out of sync with the IDP #5450

Open
carmenfan opened this issue Mar 7, 2025 · 0 comments
Open

Comments

@carmenfan
Copy link
Member

Description

Product issue: https://github.com/3drepo/3D-Repo-Product-Team/issues/638
Parent issue: #5356

We need to consider the following situations where we might potentially have a conflict in userID between 3DR and Frontegg:

Consider the user is known in both 3DR and Frontegg, then the user got removed from their teamspace and is now an orphan. By the virtue of being orphan, the user is removed from frontegg. The user is then re-added to the teamsapce:

  1. the user is known in 3DR, so from the implementation in IDP: Offload teamspace management to Frontegg #5412, we would take the userID from 3DR records and add the user to the the account, frontegg will most likely then return with a 404 not found for the userID
  2. If the user logs in, the system will check and realise that the ID is not the same as the one recorded in the database - we need a facility to just update this info.

Perhaps the best thing to do is to just remove the user from 3DR as soon as they become an orphan.

Goals

Ensure data out of sync does not cause corruption/inconsistency within the platform.

Tasks

TBC

@carmenfan carmenfan changed the title Consider scenarios where 3DR data is out of sync with the IDP IDP: Consider scenarios where 3DR data is out of sync with the IDP Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant