add TODOs for userid lookup in storage drivers #998
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, all storage drivers use the username to build a cs3 userid, which is incorrect. The UserId.OpaqueId is different from the username.
The solution is to look up the userid at the user provider, which would also address #964 needs a new CS3 call AFAICT
I tried marking relevant places in the code. The first step for really treating username and uid differently is in #996
I think this is also needed for OCM because we need to have a stable federated sharing id, which is differnt from the username because it actually should never change ...
Let me know what you think.