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.

I too am having the same issue on Brave, Firefox, Chrome, and Edge browsers.

It started last Thursday (or so).

Any help would be appreciated.

Same issue

Same, firefox

I've reported this issue to the Enpass technical team. They are currently investigating it, and I will reach out to you with updates as soon as I receive them.
#SI-3915

Hi, any update on this?

In case anyone is interested, I've found the solution: https://bitwarden.com/products/personal/.

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.

It's an Enpass issue. I switched to the free Bitwarden app and it works fine.

It's not just Chase. I'm having the same auto logon issue with my local credit union just recently also.

@alleycat Please share URL of credit union website.

On 8/9/2024 at 5:11 AM, Amandeep Kumar said:

@alleycat Please share URL of credit union website.

https://secure.rallycu.com/rallycu/uux.aspx#/login

 

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

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

On 8/9/2024 at 5:11 AM, Amandeep Kumar said:

@alleycat Please share URL of credit union website.

Forgot to add software versions.

Enpass Beta 6.11.2 (1751)

Enpass Firefox extension 6.9.4.2

Windows 10 Home 22H2

Firefox 129.0.1 (64-bit)

Problem URL https://secure.rallycu.com/rallycu/uux.aspx#/login

The extension works fine for all other sites that I use...

 

 

 

 

Is there any update that can be shared on when this issue will be fixed?

Can you give us an update on this issue?  

Our technical team has acknowledged the issue and is actively working on a solution. Fixing this bug may take some time, and the resolution will be included in the future updates of the application. 

We appreciate your patience and understanding.

Same issue. I was hoping it would be fixed by now.

 

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

Same issue here for the last 2 months, and the latest Enpass update did not bring a solution.

Same Issue (brave, edge, Chrome) any web site with login

If the form contains a username and password, it's fine. If the form is in two steps, the username is validated, but it doesn't continue the autofill.

I hope this may help the development team.

I used 2FA with Chase, and the problem only happens on the Chase front page where you enter your username and password. The username is saved on the login page so it does not have to be entered each time, but the password has to be manually retrieved within Enpass. After that login you need to request a code from Chase. When the code is delivered as a text message, I enter it on the page and the password has to be re-entered for confirmation, which on that 2FA page is automatically filled in by Enpass.

So the problem is only on the main page. It is likely that Chase and possibly alleycat's credit union have changed something that Enpass cannot properly deal with at this time.

Today Enpass 6.11.4 was released and it solved the problem of Enpass not being able to come back to the front when the application was closed with "Hide dock icon when the main window is closed".

But the update did not resolve the login problem that several here have encountered with the Chase login. alleycat, are you still having the problem with your credit union?

Any progress to report on resolving the issue, or any possible time frame to do so? It has been happening for quite a long time now.

Update? It's been a few months.   

Also www.prudential.com seems to have the same problem.