Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

🐛bug: biometric data authentication with other username in the state/loggin #24

Closed
SantiagoGaonaC opened this issue Oct 6, 2023 · 3 comments
Closed

🐛bug: biometric data authentication with other username in the state/loggin #24

SantiagoGaonaC opened this issue Oct 6, 2023 · 3 comments
Assignees
@SantiagoGaonaC
Labels
bug Something isn't working

Comments

@SantiagoGaonaC
Copy link
Member

When logging in with a username, the user logs in successfully, but when using biometric data, it is possible to enter a different user than the one registered. Therefore, the same username with which the user is logged in must be used for the biometric data submission form. To achieve this, a user state must be managed.
@SantiagoGaonaC SantiagoGaonaC added the bug Something isn't working label Oct 6, 2023
@SantiagoGaonaC SantiagoGaonaC self-assigned this Oct 6, 2023
@SantiagoGaonaC
Copy link
Member Author

User without Biometrics Enabled:

  1. You can login with username and password.
  2. If you choose to enable biometrics, the token should be saved and associated specifically to that user and if so disables access to other users.

User with Biometrics Enabled:

  1. If the token is present and the token is enabled, the token will be stored and associated specifically with that user.
  2. If the token is present and valid, it allows access via biometrics.
  3. If the biometrics fails, a username and password must be requested.
  4. You can only enter the app with the username that has the biometrics active, if you want to change username there is the possibility to change the account, but this implies that the biometrics status is deleted and the username saved, they would become temporary users until the biometrics are activated again.

@SantiagoGaonaC
Copy link
Member Author

Users using biometric authentication: The intent seems to be that if there is a valid biometric token stored, then the user will be automatically authenticated the next time they use the application.

Temporary users: The current logic suggests that, if a temporary token is present, then you immediately logout so that the temporary token is deleted, i.e., no session persistence is allowed for temporary users between uses of the application.
For CheckAuthStatus using endpoint /auth/refresh

SantiagoGaonaC added a commit that referenced this issue Oct 8, 2023
@SantiagoGaonaC
fix: temporary authentication & authentication with biometrics under …
9786656 
…states (#24)
@SantiagoGaonaC
Copy link
Member Author

Continue in #28

SantiagoGaonaC added a commit that referenced this issue Oct 10, 2023
@SantiagoGaonaC
feat: register & biometric added (#24) (#29)
b9e87f4 
* feat: new type connection to proxy (#9)

* refactor: change type variable .env

* feat: connection to the proxy via HTTP & check new endpoints

* feat: terms and conditions modal

Terms and conditions modal is added at the time of user registration.
In addition, the auto_size_text package is added for text management on different devices

* feat: validation of fields in the registration form

Implementation of the registration form fields with their validation.

* feat: validating equal passwords in form.

Password validation is done on the registration form, in addition to using modal when validating fields.

* feat: register options with merge biometricts login

registration functionality through username and password

* feat: register added (#26) & change to secure storage

* feat: customErros added of proxy response (#25)

* refactor: recome closeModalCallback

* fix: temporary authentication & authentication with biometrics under states (#24)
SantiagoGaonaC added a commit that referenced this issue Oct 10, 2023
@SantiagoGaonaC
chore(0.1.1): added authentication capabilities (#30)
8acdeae 
* feat: register & biometric added (#24) (#29)

* feat: new type connection to proxy (#9)

* refactor: change type variable .env

* feat: connection to the proxy via HTTP & check new endpoints

* feat: terms and conditions modal

Terms and conditions modal is added at the time of user registration.
In addition, the auto_size_text package is added for text management on different devices

* feat: validation of fields in the registration form

Implementation of the registration form fields with their validation.

* feat: validating equal passwords in form.

Password validation is done on the registration form, in addition to using modal when validating fields.

* feat: register options with merge biometricts login

registration functionality through username and password

* feat: register added (#26) & change to secure storage

* feat: customErros added of proxy response (#25)

* refactor: recome closeModalCallback

* fix: temporary authentication & authentication with biometrics under states (#24)
SantiagoGaonaC added a commit that referenced this issue Oct 11, 2023
@SantiagoGaonaC
fix: user state biometric (#33)
117c856 
* feat: new type connection to proxy (#9)

* refactor: change type variable .env

* feat: connection to the proxy via HTTP & check new endpoints

* feat: terms and conditions modal

Terms and conditions modal is added at the time of user registration.
In addition, the auto_size_text package is added for text management on different devices

* feat: validation of fields in the registration form

Implementation of the registration form fields with their validation.

* feat: validating equal passwords in form.

Password validation is done on the registration form, in addition to using modal when validating fields.

* feat: register options with merge biometricts login

registration functionality through username and password

* feat: register added (#26) & change to secure storage

* feat: customErros added of proxy response (#25)

* refactor: recome closeModalCallback

* fix: temporary authentication & authentication with biometrics under states (#24)

* fix: state invalid in login-screen (#28)
SantiagoGaonaC added a commit that referenced this issue Oct 11, 2023
@SantiagoGaonaC
🐛chore(0.1.4): fixed invalid state in login-screen and biometric state (
28aa9c0 
#34)

* fix: user state biometric (#33)

* feat: new type connection to proxy (#9)

* refactor: change type variable .env

* feat: connection to the proxy via HTTP & check new endpoints

* feat: terms and conditions modal

Terms and conditions modal is added at the time of user registration.
In addition, the auto_size_text package is added for text management on different devices

* feat: validation of fields in the registration form

Implementation of the registration form fields with their validation.

* feat: validating equal passwords in form.

Password validation is done on the registration form, in addition to using modal when validating fields.

* feat: register options with merge biometricts login

registration functionality through username and password

* feat: register added (#26) & change to secure storage

* feat: customErros added of proxy response (#25)

* refactor: recome closeModalCallback

* fix: temporary authentication & authentication with biometrics under states (#24)

* fix: state invalid in login-screen (#28)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SantiagoGaonaC SantiagoGaonaC

Labels
bug Something isn't working
Projects
atlanta - Frontend
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SantiagoGaonaC