ConnectID Foundation #2847
Open
ConnectID Foundation #2847
Conversation
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
Added database models and helper class for storage (with upgrader). Added network helper class to wrap common functionality for API calls. Added code to support encryption via a key stored in the Android Keystore.
…ort test framework
OrangeAndGreen
requested review from
ctsims,
shubham1g5,
avazirna and
pm-dimagi
|
@damagatchi retest this please |
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.
Summary
Foundational code for ConnectID, primarily consisting of database, network, and encryption code.
This code will support ConnectID when it is integrated into the codebase.
Currently the code in this PR is compiled, but almost completely uncalled.
Product Description
Safety Assurance
The code in this PR is currently not called from anywhere, except:
The EncryptionKeyProvider is created and stored, but never used
Automated test coverage
Unit tests created for the encryption code