Jump to content
Enpass Discussion Forum

Recommended Posts

Posted

Hi,

I'm a web developper and I use Enpass frequently to login on my local app with different test accounts.

One of the last version of the app broke the autofill on local website (when the exact same build works on the remote URL).

Environment:

  • OS: macOS Monterey v12.6
  • Browser: Google Chrome v111.0.5563.64
  • Chrome extension: Enpass Password Manager v6.8.3
  • Enpass version: 6.8.5 (1256) Mac App Store

PS: the issue is also present on another computer with Windows 11

Scenario:

I prepared a scenario you can reproduce on your side too. I used the RealWorld demo app so that you can reach it remotely and run locally as well.

  1. Create an entry in enpass with the following. Note that I created this account on the app:
    image.png.9ed7c56216947b3b98bf747459f020a9.png
  2. Go on the login page on the remote website: https://demo.realworld.io/#/login
  3. Select the account
    image.png.feaf5c863aaa3f705df998a4ce4c7f25.png
    image.png.31767d952135be457bc711060028b9d7.png
    The autofill works as expected.
  4. Now open a terminal and run
    git clone https://github.com/mutoe/vue3-realworld-example-app.git
    cd vue3-realworld-example-app
    npm install
    npm run dev
     
  5. It should download, install and run the RealWorld demo app locally. Now reach the address displayed in the terminal. For me it's http://127.0.0.1:5173/
  6. Go on the login page and select the login proposed by the extension
  7. Nothing happened. The field is not filled as expected

Thanks for your help,
Aurelien

  • 4 weeks later...
Posted (edited)

Any update on the matter? I am in the same boat, web developer who frequently Enpass with `localhost` and this breaks the workflow hard. 

Edited by Blackfox
Capitalize Enpass name
Posted

Hi @aurelien.rasse

Our development team is aware of this bug and they are working on fixing it. I will be unable to share any ETA at the moment but will be sure to update this forum once a patch addressing this issue is released. We appreciate your kind understanding and patience in the interim.

  • Haha 1
  • 2 weeks later...
  • 4 weeks later...
  • 2 months later...
  • 1 month later...
Posted

Hi @all

While addressing this bug, we have determined that the autofill failure is linked to a protocol change in this scenario. To resolve this issue, could you kindly save an alternative URL with the 'HTTP' protocol in your Item for locally served websites and then share your observations with us?

Posted

Hi,

Indeed, it works!

Finally a solution, I'm gonna save a lot of time.

Is this because the domain name is matched only with HTTPS by default? If yes, would it be possible to add a setting to allow matching over HTTP too?

Thanks,

Aurélien.

  • 2 weeks later...
Posted
On 9/22/2023 at 1:55 PM, Abhishek Dewan said:

Hi @all

While addressing this bug, we have determined that the autofill failure is linked to a protocol change in this scenario. To resolve this issue, could you kindly save an alternative URL with the 'HTTP' protocol in your Item for locally served websites and then share your observations with us?

Could you expand a bit on how to achieve this? I have added multiple versions (screenshot attached) but still not getting completions. 1204396983_Screenshot2023-10-11at17_16_38.thumb.png.cf92b41d73a6c42e38bf29cb1042d796.png

  • 2 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...