FINERACT-2641: Implement Authentication Feature#16
Merged
Conversation
- implemented jwt auth - used ES256 for asymmetric jwt generation - 2FA implemented with OTP - device fingerprints checked in login - password and username columns added - passwords hashed with bcrypt - generate jwt key script
- added more tests for infrastructure, user features
- adjusted registration and users features and cucumber tests to match
Member
|
@edk12564 I cannot see swagger specs in this for your apis |
Aman-Mittal
approved these changes
Jun 14, 2026
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
2 participants
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.
JIRA: FINERACT-2641
Summary
This is the authentication/login feature of fineract-consumer-facing. The goal is to implement the beginnings of a modern consumer frontend auth process with security in mind.
Items implemented:
Detailed Summary: