-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Integrate VeraId in account creation process (#43)
LTR-60 # High-level changes - Migrated to production environment (by updating connection params in `server_connection_params.der` file). - When communicating with the server, instead of requesting a VeraId id (e.g., `[email protected]`), we now request a user name (e.g., `alice`) in the current locale (e.g., `en_GB`) -- the user may be running a (very) old version of the Letro app, which may not reflect the latest set of domain names supported by Relaycorp's Letro server. - Renamed instances of "veraId" to "veraidId" for legal reasons (we have the trademark for "VeraId", not "Vera", which belongs to a third party). I didn't change all occurrences -- only the ones I worked with. - I removed 2-3 classes related to the `AwalaMessageParser` implementation for account creation messages, as they seemed unnecessary. ## Changes to ignore I'd recommend ignoring the following packages during review: - `tech.relaycorp.letro.server.messages`: ASN.1 DER serialisation of [Letro server](https://docs.relaycorp.tech/letro-server/) messages, such as [account creation](https://docs.relaycorp.tech/letro-server/account-creation); the final version of the contact pairing serialisers will be moved there. - `tech.relaycorp.letro.utils`: Various Letro-agnostic utilities related to ASN.1, cryptography, etc.
- Loading branch information
Showing
46 changed files
with
1,708 additions
and
164 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.