feat(pre-created-users): pass new generated kyber key replacePreCreatedUser#528
Merged
apsantiso merged 1 commit intoApr 18, 2025
Merged
Conversation
…created user function
36c89b8 to
dfb6d4d
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.



This passes the frontend generated new public kyber key to the replace precreated user function so any pre created user that has hybrid invitations and already existent private and public kyber keys can process those invitations.
Note: this flow is not going to be possible unless we start returning the public kyber key when precreated users are generated, so all the guest sharings are still being handled using ECC encryption for the moment.