-
-
Notifications
You must be signed in to change notification settings - Fork 199
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.
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
Feature Request - Pin Code #288
Comments
I would also love to see this feature added. I recently switched from Authy, and I loved being able to unlock the app with a PIN code rather than having to enter a long password every time. I have also recently tried andOTP and 2FAS which both offer this feature, but I prefer the user interface of Authenticator Pro. I really like the use of color, the flexible layout, and the countdown sliders. It would be really nice if I only had to enter my password after a reboot and then be able to unlock the app with a PIN code the rest of the time. I am not a fan of biometic features, so I never use them, but I would appreciate having the option to set a PIN code instead. |
+1 |
I would also love to see this feature on the Wear OS version |
Is your feature request related to a problem? Please describe.
I'd like to use password/pin instead of password/biometric to unlock the app. Passwords tend to be long so entering them can be a pain if using the app frequently.
Describe the solution you'd like
Option to use a numeric PIN code along with the password.
Additional context
andOTP has a similar feature where you can use a PIN code and password but the issue there is it can be "brute forced" as there is no limit to wrong attempts with the pin code, it just closes the app each time wrong code is entered.
A feature like BitWarden Vault's access would be nicer. You have a master password you can use and then you can also use a PIN code to quickly unlock the vault. PIN code gives you 5 (10?) failed attempts before it is disabled and you are forced to enter the master password.
The text was updated successfully, but these errors were encountered: