paulsiu

I am reporting that the latest extension 6.11.0 fixed the issue on Chrome on ChromeOS, and firefox on MacOS and Linux. What change is when you click on continue to the 2FA prompt, you get a prompt to press the hardware key button. Previously, the popup never appear and you get stuck. I like to thank the enpass team in fixing this issue. I will report this to the firefox forum.

Notice there was an update today, but unfortunately it did not resolve the issue. Thanks for the update.

Update, I replicated this issue under ChromeOS and Chrome browser. Just to make sure the problem is understood. When you log into icloud, a prompt for the hardware key appears and then you press the hardware key to login. When enpass browser extension is enable, the iCloud popup for hardware key will not appear and you won't be able to login. If you disable the enpass extension, the issue goes away. The browser extension appears to prevent the hardware key popup.

I have posted this same issue several months ago and have been waiting for the fix.

The question was posted back close to a month ago. Will Enpass be able to give a solution to the issue any time soon?

To replicate, you must have an icloud account that uses hardware key as 2FA. The following is the expected behavior Open browser and go to https://icloud.com. Log into your Apple account. The site will prompt you to press the button on the hardware key and also prompt you for the hardware key's PIN. User enter the PIN and the browser logs you into the apple account. However, if the enpass extension is installed, step 3 does not prompt for the pin and there is a spinning progress circle that never goes away. It is definitely the enpass extension, since removing it allows it to work. The following are the configuration Platform: Apple M1, MacOS Sonoma 14.5 Enpass desktop version: 6.11.0 Enpass Extension version: 6.9.4.1

Following up, is there any news? As for config Platform: Linux and MacOS Enpass desktop version: 6.10.1 (1661) Enpass Extension version: 6.9.4.1

I have made some attempt to rename the user name and password fields thinking that Chase is using non-standard fields, but that didn't seemed to fix the issue.

I have notice that recently that autofill to chase bank has stopped working. Any idea what might be at fault and how to work around it? https://secure.chase.com/web/auth/dashboard#/dashboard/overviewAccounts/overview/index I am using firefox, but I don't think this is a browser issue but more of a site field issue.

Hi I am following up again to see if there is any progress on the bug.

I am asking again to see what the status is. It feels like that this fix request has been abandoned.

Hi, I am following up to see if Enpass has a fix for this issue?

OK, I encountered the issue again today. I still don't know what triggers it.

Note that I am having the same issue on Linux PopOS 22.04. Initially I thought I had to reinstall the enpass and extension, but I have done that 3x already and the issue did not go away. One workaround so far is to make sure tha the enpass desktop is unlock and then disable the extension in firefox and then re-enable it. This seems to fix the issue temporary.

OK, Thank you. I will be waiting eagerly for the fix.