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.

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

Autofill always asks for master password, unless "session timeout" is set to "never" #1167

Open
1 task done
michaelwimmer opened this issue Nov 25, 2024 · 7 comments
Open
1 task done
Labels
bug Something isn't working

Comments

@michaelwimmer
Copy link

Steps To Reproduce

  1. Set up autofill as requested in the bitwarden app
  2. Set the "Session timeout" to 15 minutes
  3. Make sure "Unlock with Face ID" and "Unlock with PIN code" are deactivated
  4. Go to a website with a login
  5. Try to autofill (tapping e.g. the "Passwords" button on the onscreen keyboard): the Bitwarden autofill window opens.
  6. Enter the master password
  7. Go to another website login
  8. Tap on 'Passwords' before the 15 minutes have passed
  9. Bitwarden autofill window opens again, asking again for the master password

Expected Result

Bitwarden should not ask for the master password again, if the second time it is opened falls into the window set by "Session timeout".

Actual Result

Bitwarden always asks for the master password.

The only way I could avoid this is by setting in step 2 "Session timeout" to "never". Then autofill never asks for the master password.

However, this is obviously not an ideal setting.

Screenshots or Videos

No response

Additional Context

This behavior of the bitwarden autofill is especially annoying for logins that span two pages, such as gmail. Then you have to enter the master password twice for one login.

One can find similar reports e.g. on reddit (see below) since quite a while. Typically, the advice is to use biometrics. Indeed, if I enable biometrics, bitwarden will scan my face every time in autofill. However, I would prefer to avoid using Face-ID for various reasons. Also, given that "never" actually works as expected, any other session timeout should work, too.

Examples of similar issues reported online:

Build Version

Version 2024.11.0 (1680)

What server are you connecting to?

EU

Self-host Server Version

No response

Environment Details

  • Device: IPad Pro (11-inch, second generation)
  • IPadOS Version: 18.1

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@michaelwimmer michaelwimmer added the bug Something isn't working label Nov 25, 2024
@francoposa
Copy link

+1 I am also experiencing this. The autofill is really the only way I ever interact with Bitwarden on the phone, so this issue is not an afterthought, it is really frustrating.

@mudtar
Copy link

mudtar commented Dec 8, 2024

I am also experiencing the same issue.

@kholisrag
Copy link

have same issue here, I have iOS with disabled FaceID, the iOS autofill always ask for master password instead off PIN

@tanguylegazon
Copy link

I have the same issue on iOS:

  • iPhone XR
  • iOS 18.2 (22C152)
  • Bitwarden 2024.12.0 (1740)

@mel-m
Copy link

mel-m commented Dec 14, 2024

I have the same issue and hope this gets resolved soon. I have Face ID enabled but even needing to do a face scan multiple times is too unusable.

Version: 2024.12.0 (1740)

-------- Device --------

Model: iPhone14,7
OS: iOS 18.1.1

------- CI Info --------

Branch: release/2024.12-rc1
CI Run Attempt: 1
CI Run ID: 12126636763
CI Run Number: 433
Commit hash: c621b02
Compiler Flags:
Repository: https://github.com/bitwarden/ios

@mtalhakrc
Copy link

+1. Autofill is asking for confirmation on every attempt without respecting to the session timeout

@Greenderella
Copy link
Member

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants