aurelien.rasse Posted March 24, 2023 Report Posted March 24, 2023 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. Create an entry in enpass with the following. Note that I created this account on the app: Go on the login page on the remote website: https://demo.realworld.io/#/login Select the account The autofill works as expected. ✅ 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 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/ Go on the login page and select the login proposed by the extension Nothing happened. The field is not filled as expected ❌ Thanks for your help, Aurelien
Abhishek Dewan Posted March 27, 2023 Report Posted March 27, 2023 Hi @aurelien.rasse Welcome to the Enpass Forums. I have forwarded this concern to our dedicated team and will get back to you soon with an update. We appreciate your patience in the meantime. #SI-3318
Abhishek Dewan Posted March 30, 2023 Report Posted March 30, 2023 Hi @aurelien.rasse We have reproduced the bug on our end due to which this issue is occurring. Our dedicated team is now working on resolving it and soon a patch addressing this issue will be released. Thank you for your patience in the interim.
Blackfox Posted April 24, 2023 Report Posted April 24, 2023 (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 April 24, 2023 by Blackfox Capitalize Enpass name
aurelien.rasse Posted April 28, 2023 Author Report Posted April 28, 2023 Hi, Do you have some news about this issue? It's been one month now and I can't wait for this bug to be solved! Thanks
Abhishek Dewan Posted April 28, 2023 Report Posted April 28, 2023 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. 1
TommyTomTom Posted May 11, 2023 Report Posted May 11, 2023 I would appreciate a fix too, this has been going on for a very long time now.
aurelien.rasse Posted June 6, 2023 Author Report Posted June 6, 2023 Hi @Abhishek Dewan Would you have some news about this issue? It's still annoying me every day Thanks
aurelien.rasse Posted August 8, 2023 Author Report Posted August 8, 2023 Hi, Some news about this? Thanks
Blackfox Posted August 15, 2023 Report Posted August 15, 2023 Same old, any update? It's been almost whole summer something that used to work no longer does.
Abhishek Dewan Posted September 22, 2023 Report Posted September 22, 2023 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?
aurelien.rasse Posted September 26, 2023 Author Report Posted September 26, 2023 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.
Abhishek Dewan Posted September 27, 2023 Report Posted September 27, 2023 Hi @aurelien.rasse I'm glad to hear that this issue has been resolved for you! Moreover, we are also working on a fix for HTTP pages which will be available in the future versions. We request you to kindly bear with us until then.
Blackfox Posted October 11, 2023 Report Posted October 11, 2023 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.
Victor Posted January 8, 2024 Report Posted January 8, 2024 I'm here to complain about how this isn't working yet, running 6.9.3 1591. ETA?
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now