Add support for sha256 and test cases #73
Merged
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
spacepirate0001
changed the title
spacepirate0001
changed the title
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 update introduces a new sha256 field in your resource schema to store the SHA-256 hash of the password concatenated with a salt. The hashing process is added to the
repopulateHashesfunction where the SHA-256 hash is calculated and set in the resource data. Make sure to include error handling and validation as needed.Added test ensures that:
Each hash attribute (sha256, sha512, apr1, bcrypt) is computed and set as expected based on the input password and salt.
It validates the creation of the password resource with all computed hash outputs.
Closes #72