Content
View differences
Updated by Wieland Lindenthal almost 2 years ago
As a side effect of deleting possibly broken OAuthClientTokens is that we lose the remote user identifier (origin\_user\_id) and therefore they are removed from AMPF folders.
By decoupling the two of them, we can keep the remote identifier around even if the token is missing.
This will require changes to:
1. `ConnectionManager` as the piece of code that create the tokens
2. `ProviderSyncServices` as they rely on the remote identifier
3. `FileLinkCreate/UpdateService` as they rely on the remote identifier
4. All of `NextCloud` commands and queries as the URLs are dependent on the identifier
QA is complex and was done by developers // <mention class="mention" data-id="96697" data-type="user" data-text="@Cécile Guiot">@Cécile Guiot</mention>
By decoupling the two of them, we can keep the remote identifier around even if the token is missing.
This will require changes to:
1. `ConnectionManager` as the piece of code that create the tokens
2. `ProviderSyncServices` as they rely on the remote identifier
3. `FileLinkCreate/UpdateService` as they rely on the remote identifier
4. All of `NextCloud` commands and queries as the URLs are dependent on the identifier
QA is complex and was done by developers // <mention class="mention" data-id="96697" data-type="user" data-text="@Cécile Guiot">@Cécile Guiot</mention>