Unsigned builds continuously prompt for keychain password when accessing logins/creditcards/syncing etc
Categories
(Toolkit :: Form Autofill, defect)
Tracking
()
People
(Reporter: mtigley, Unassigned)
References
Details
Attachments
(2 files)
Steps to Reproduce
- On a new profile, save a credit card from about:preferences
- Firefox will prompt for keychain password. Click "Allow"
Expected
Credit card is saved when keychain password is successfully authenticated.
Actual
Firefox will prompt the user several more times for the keychain password even though it was successful the first time.
Some notes: this issue goes away when clicking "Always Allow".
Comment 1•2 years ago
|
||
Similar experience when syncing (and I think even when uploading existing local cards, so not limited to saving) - but let's see if that gets fixed as a side-effect of fixing this before we open a secondary issue.
Comment 2•2 years ago
•
|
||
It seems that every OSKeystore API call that requires accessing "Firefox Encrypted Storage" keychain access triggers two prompts, and the result is not cached so if we call the API multiple times, each API calls trigger two prompts.
For example, if users save a credit card, then the user will see 4 prompts:
- Formautofill module calls encrypt to encrypt the credit card number
- Trigger the 1st prompt because ensureLoggedIn -> nativeOSKeyStore.asyncSecretAvailable
- The dialog says "Firefox wants to use your confidential information stored in Firefox Encrypted Storage in your keychain"
- After the user types the password and presses ok, then the 2nd prompt appears, with a little bit different description in the dialog
- The dialog says "Firefox wants to access key Firefox Encrypted Storage in your keychain"
ensureLoggedIn
finishes, but triggers the 3rd prompt because of nativeOSKeyStore.asyncEncryptBytes- The same as step3, after the user types their password, another dialog appears (4th)
- Encrypt finishes
Note. This doesn't seem to be recent regression, I tried Fx106 and I could still this issue, maybe this is caused by an OS updated?
Hi dana,
This issue is quite annoying for users, is anyone in your team could help take a look at this bug? Thanks!
Comment 3•2 years ago
|
||
Comment 4•2 years ago
|
||
Comment 5•2 years ago
|
||
From a discussion in slack, it seems the dialogs shown in those screen-shots only happen with local builds, not with official builds. I'm guessing the distinction might be more like "signed" vs "unsigned" builds, and that it's the OS showing this dialog?
![]() |
||
Comment 6•2 years ago
|
||
Yeah, this is an OS thing. I'm not aware of anything Firefox can do to affect this behavior when unsigned. I recommend using "Always Allow".
Comment 7•2 years ago
|
||
I think my comment on slack caused this to be opened - thanks! But there's nothing for us to do here.
Description
•