feat: e2ei: Respect E2EI creating mls client fixed certificate status #2457
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.
Just a cherry-pick of closed PR .
Some problems occurred there as original target branch was merged into RC and that one wasn't updated there are a lot of changes and conflics, so it's easier to remove that branch and cherry-pick a new one with only changes that are actually related to the commit message.
What's new in this PR?
Issues
Even when the device (client) has E2EI certificates it's displayed as not valid
Causes (Optional)
WireIdentity.clientId
that CoreCrypto returns for each Client is not a usualClientId
but combination ofClientId
andUserId
, so when app was checking if client has a certificate -> there is no certificate for such clientId.Solutions
Fix the
GetUserE2eiCertificatesUseCase
to return not just a Map, but a result that allow to get if client has a certificate by our regularClientId
.