Open Bug 1626247 Opened 5 years ago Updated 2 years ago

[macOS] The operating system’s authentication dialog accepts the empty password only at the second attempt

Categories

(Firefox :: about:logins, defect, P3)

76 Branch
Desktop
All
defect

Tracking

()

Tracking Status
firefox76 --- wontfix
firefox77 --- affected

People

(Reporter: cmuntean, Unassigned)

References

Details

(Whiteboard: [passwords:os-reauthentication])

[Affected versions]:

  • Firefox Nightly 76.0a1 (Build ID: 20200331093527)

[Affected Platforms]:

  • Mac 10.15.3
  • Mac 10.14.6
  • Mac 10.13.6

[Prerequisites]:

  • Have a profile with at least one saved login.
  • Have an empty OS password set.

[Steps to reproduce]:

  1. Open the latest Nightly Firefox browser.
  2. Navigate to the "about:logins" page and select a saved password.
  3. Click on the "Show Password" button from the login item.
  4. Click the "OK" button of the OS auth dialog.
  5. Observe the behavior.

[Expected result]:

  • The password is correctly shown without entering any password.

[Actual result]:

  • The operating system’s authentication dialog is re-displayed and only at the next attempt the dialog accepts the empty password and the password of the saved login is shown.

[Notes]:

  • The issue is also reproducible after clicking the "Copy" and "Edit" button.
  • The issue is also reproducible if trying to check the "Use a master password" option from "about:preferences#privacy" page.
  • No errors are displayed in the browser console.
  • Attached a screen recording with the issue: link.

I looked in to this as did :spohl and we both couldn't find a fix for this. I will keep this bug open but for the time being this appears to be something we will have to just consider as a "known issue".

Priority: -- → P2

Sir may I contribute on this issue?

I am doing this for the first time so I may ask you for little help

Whiteboard: [passwords:os-reauthentication]

Moving to P3 as this is not happening in the next release cycle.

Priority: P2 → P3

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: blocker → --

The severity field is not set for this bug.
:serg, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(sgalich)
Severity: -- → S3
Flags: needinfo?(sgalich)
You need to log in before you can comment on or make changes to this bug.