1582492 - The "enter keychain password" panel is no longer triggered a second time if a wrong password was submitted then denied when importing passwords from Chrome

Status: NEW

(Firefox :: Migration, defect, P3)

Description

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Attachment: keychain password panel no longer triggered.mov

[Notes]:

• On the following attempts for importing passwords from Chrome, the "enter keychain password" panel is no longer displayed and the "Import Complete" message is displayed on the "Import Wizard" window even if the passwords are not imported.
• The issue is still reproducible even if the browser is restarted.
• The "enter keychain password" panel is triggered again only after restarting the OS.

[Affected Versions]:

• Nightly 71.0a1

[Affected Platforms]

• All Mac

[Prerequisites]:

• Have a password set for the OS's account.
• Have multiple saved passwords in Chrome.

[Steps to reproduce]:

1. Open the latest Nightly browser, navigate to "about:logins" page and click the "Settings" button.
2. Click the "Import Passwords..." option, Select "Chrome" and click the "Continue" button.
3. Click the "Continue" button.
4. Enter a wrong password in the displayed panel and click the "Allow" button.
5. Click the "Deny" button.
6. Try to import again the passwords from Chrome and observe the behavior.

[Expected results]:

• The "enter keychain password" panel is displayed.

[Actual results]:

• The "enter keychain password" panel is no longer triggered and the "Import Complete" message is displayed on the "Import Wizard" window even if the passwords are not imported.

[Additional Notes]:

• On Windows, this issue is not reproducible since no "require keychain password" panel is displayed.
• Attached a screen recording of the issue.

Comment 1

[Matthew N. [:MattN]]

Thanks for filing. I don't think there is a way to force the dialog to re-appear so all we could do is message the user to log out or restart.

I hope this is an edge case as the timing and wording of the dialog should make it clear that a correct password is necessary. Bug 706008 would fix the issue of claiming things were successful. For this bug we could add some preemptive text to go along with the text about closing the other browser and/or show some text when we get an exception from the keychain code.

We can also document this on SUMO.