MaxM
-
Posts
24 -
Joined
-
Last visited
-
Days Won
13
Posts posted by MaxM
-
-
3 hours ago, DJg450 said:
The issue still persists... Also setting up new accounts, was not working. Strangely, alrady set up webdav accounts are working with some people...
Ditto! Similar behavior for me as well.
- 1
-
On 5/3/2022 at 12:45 AM, Mohit Thapa said:
Hi @Mohit Thapa
I'm afraid the issue still exists in the Windows store version 6.8.0 (1048). Connection to WebDAV failing with a generic message "Could not connect to specified WebDAV folder. Check you username and password". Note that I can connect to the WebDAV folder in question from a non-Windows store version of Enpass or from Windows Explorer directly. So the problem is definitely not in credentials or URL.
- 2
-
Hello. Since updating to 6.8.0 (1002) I'm getting an error 906405 when trying to sync with my WebDAV server. If I switch to Windows Desktop version the problem disappears.
Any way to fix it?
-
9 hours ago, Anshu kumar said:
Hi guys,
Thanks for writing in.
As we have mentioned in the blog post, "The UWP app will be available on the Windows Store until our next major update. At that time, the bridged app would have all the functionality of the UWP app along with signature Windows 10 experiences.
Thanks!
@Anshu kumar, thank you for pointing this out. Let me to rephrase the question then: is there a beta of the bridged app?
-
Just now, havenerd said:
Yes, the Enpass 6 Beta for Windows 10 can be downloaded from this page Enpass 6 Beta Downloads
No, it can't. There is only Traditional Windows version, but no UWP.
Here is the quote about UWP beta versions from https://www.enpass.io/beta-program/ page:
QuoteWindows 10- Desktop (Bridged app): Beta versions for Enpass Password Manager will be distributed through PackageFlight, so it's mandatory that you provide your Microsoft Account ID (E-mail) while subscribing for Beta program
The reason for my post was that I've subscribed for Beta program but never received a UWP beta.
-
Is it possible to use Edge Enpass extension with Windows Desktop Enpass 6 beta? Or will it require a new extension?
-
I've subscribed to UWP Enpass 6 Beta about a month ago but never received a link for download. Does Win10 beta version even exists?
-
On 5/27/2016 at 5:54 AM, Vikram Dabas said:
Hi @MaxM and @kevin.purcell
I am sorry for the inconvenience caused to you. Enpass can detect only the login forms on any page and auto-fill Username/Email/ Password fields, while all other fields would remain empty. We have plans to work on an improved version with complete Form-filling that will save all the fields from the page inside Enpass keychain.
I can't assure any ETA for this and only can say that it will be available in any of future versions. Please bear with us. Cheers!
Hi @Vikram Dabas and Enpass Development Team
Any updates on adding an ability to populate more than 2 fields on a login webpage?
-
-
@Anshu kumar any update? The issue continues to happen intermittently on both Nexus 7 and Nexus 6P.
-
As of recently autofilling for Royal Bank of Canada online banking site has stopped working in Chrome. I've tried both stable version 5.3.0.1 and beta version 5.3.1.1 to no avail. With the latter autofilling works fine in Edge.
It definitely has worked fine before in Chrome.
Here is the URL: https://www1.royalbank.com/cgi-bin/rbaccess/rbunxcgi?F6=1&F7=IB&F21=IB&F22=IB&REQUEST=ClientSignin&LANGUAGE=ENGLISH
This might be a problem with Enpass or something changed at RBC site. Not sure...
OS: Windows 10
Chrome: latest (v 52.0.x)
Enpass: Desktop v.5.3.0.1 and Desktop Beta v 5.3.1.1 -
3 hours ago, Anshu kumar said:
Thanks for update @MaxM. We will look into this issue.
I just observed the same issue happening on Nexus 7 tablet with password authentication. I've entered master password to unlock Enpass and it requested the password again. I switch away and then back to the app and it's unlocked. So the issue is not related to the fingerprint auth but to Enpass unlocking mechanism in general.
Android 6.0.1 June patch level
-
24 minutes ago, Anshu kumar said:
Hi @MaxM,
Sorry to hear about the trouble. We have been unable to reproduce this issue here, although we'll keep a close eye on it. Could you please try rebooting your phone and see if that solves the issue?
@Anshu kumar, the issue reoccurs after reboot. Once again, it's not happening every single time but rather once in a while.
-
I'd like to report an issue I'm sometimes experiencing with Enpass autofill notification. My phone supports fingerprint unlock and naturally I've configured Enpass to use it as well.
In some cases after unlocking Enpass autofill notification using fingerprint auth the app re-requests unlock again. I.e. it looks like fingerprint auth was successful but for some reason Enpass doesn't show the list of logins but goes back to fingerprint authentication screen.
What's even more interesting is that if I switch away from Enpass at this point and then come back to it it would be already unlocked.
Nexus 6P with Android 6.0.1 + June security patch level.
-
2 hours ago, kevin.purcell said:
I wish I could say that your suggestion works, but I double checked the fields and they are username, password, and organisation ID. Even though the username and password fields are the proper type nothing is filled out in Chrome when I click on the login.
@kevin.purcell you may want to share the website name so that Enpass staff can investigate in details.
-
-
3 hours ago, Vikram Dabas said:
Hi @MaxM and @kevin.purcell
I am sorry for the inconvenience caused to you. Enpass can detect only the login forms on any page and auto-fill Username/Email/ Password fields, while all other fields would remain empty. We have plans to work on an improved version with complete Form-filling that will save all the fields from the page inside Enpass keychain.
I can't assure any ETA for this and only can say that it will be available in any of future versions. Please bear with us. Cheers!
Vikram Dabas, thanks for the update. I understand Enpass is still a work-in-progress and I'm ok with waiting to see all the functions implemented.
There are many sites out in the internet that feature advanced login forms with 3 or 4 fields that have to be filled in. While I understand why you refer to this feature as form-filling I think this requirement may need to be treated separately and possibly assigned a higher priority than a full-blown form-filling.
Offtopic: how in life do you quote one's name in the reply on this forum???
-
12 hours ago, kevin.purcell said:
I have a banking website that has something similar. The site has 4 fields:
- Country (Drop Down - Automatically populated)
- Organisation ID
- User ID
- Password
Enpass does not fill in anything for this site. I even tried deleting the login and entering the password, but Enpass doesn't even seem to pick up that the login needs to be saved. 1password was working for everything except the Organisation ID which I would have to copy/paste in manually.
kevin.purcell, check the type of User ID and Password fields for this site in Enpass. User ID should have type "Username" and Password should have type "Password". This should get you at least these two fields populated.
-
I have a site where i need to fill in 3 fields in order to log in: 2 different ID fields and the password. The problem is I can't figure out how to do it with Enpass. When I was using Roboform it was able to handle this without a problem.
Here is the site: https://www.dayforcehcm.com
I need to fill in Company and User Name fields of "text" and "numeric" types respectively and also fill in the Password field. At best I was able to fill in User Name and Password. I can't fill in Company field via Enpass no matter what I tried.Any suggestions are appreciated.
- 3
-
7 hours ago, Yogesh Kumar said:
This is what I should say very unusual behavior as Enpass works very well with Chrome Browser. We highly recommend that browser verification must be enabled for supported browsers to validate their code signatures. One of the possible cause could be some firewall or antivirus is there and preventing the communication between Enpass and Enpass Browser Extension, as a result you are getting "Enpass Conneciton Error". I suggest you to check your antivirus/firewall settings if they are blocking localhost address 127.0.0.1. Please let us know, if problem still persist.
Yogesh, thank you for your feedback. It doesn't look like the communication is blocked by the firewall or an antivirus. After re-enabling browser verification in Enpass I'm seeing the following message in Windows Security Event log around the moment when I click on Enpass extension icon in Chrome :
The Windows Filtering Platform has permitted a connection.
Application Information:
Process ID: 18376
Application Name: \device\harddiskvolume2\program files (x86)\enpass\enpass.exeNetwork Information:
Direction: Inbound
Source Address: 127.0.0.1
Source Port: 10391
Destination Address: 127.0.0.1
Destination Port: 53980
Protocol: 6Filter Information:
Filter Run-Time ID: 68036
Layer Name: Receive/Accept
Layer Run-Time ID: 44However the browser then shows an error page saying Enpass Connection Error. I confirm that Enpass fails to connect to Chrome browser on both Windows 7 and Windows 10 with browser verification enabled.
Just to think about this, why would firewall be the culprit if the communication works when the validation is disabled. I mean, Enpass browser extension still has to connect to Enpass main program no matter whether validation is enabled or disabled, right?
As I've mentioned above I'm running the latest Chrome v. 50.0.2661.102
Let me know if you'd like me to try anything else.
-
21 minutes ago, Christoph said:
So are you saying that autofill now works for you? Because in my case Enpass has no problem identifying the website but it does not fill in the fields unless you manually activate the "autofill" by cicking on the Enpass button and selecting the relevant entry.
I see what you saying.., No, I also have to click on Enpass icon and manually activate the "autofill" by clicking on the relevant entry.
-
Ok, I've figured out what (a part of) the issue was. I have all my logins imported from Roboform using Roborom's Print / Save as HTML feature. The problem is that Roboform inserts soft hyphen characters ­ to every single data field (URL, username, password, etc.) in the HTML file.
When Enpass imported the data from Roboform's HTML file it imported soft hyphens but treated them as invisible characters. As a result Enpass couldn't match any imported entry to the existing sites and failed to autofill any entries.
I have partially rectified the issue by removing all entries of "­" (soft hyphens) from the HTM file before importing into Enpass.
Now autofill works on some of the sites.There is still at least one site where autofill didn't work until I edited the data manually. For one of my banks login data was stored in Roboform in the following fields:
k1: <card number>
q1: <password>So when Enpass imported this entry from the HTML file it failed to recognize k1 field as Username and q1 as Password. I have manually changed in Enpass the field types to respectively Username and Password and got autofill working.
I'm sure there will be many more entries like this where Enpass didn't assign proper field type.I'd like to see Enpass importing algorithm improved to:
- Remove soft hyphens from Roboform export data
- Improve recognition of username and password fields
-
I've just installed Enpass few days ago to try and see if it's any better than Roboform I'm currently using. The biggest challenge / drawback I'm seeing right now is that autofill doesn't work at all in Chrome. I'm using the latest version of Chrome and no matter what I tried the autofill isn't working.
At first Enpass extension for Chrome wouldn't work reporting "Enpass Connection Error" but I was able to rectify it by disabling browser verification in settings. However autofill still is a no go.
I'm using Windows 7 x64 / Chrome 50.0.2661.102 m (64-bit) and Windows 10 x64 / Chrome 50.0.2661.102 m with the same result on both systems.
Browser extension open a new tab
in Windows PC
Posted
Not trying to steal the OP's thread, but I just wanted to confirm that I'm having the same issue with a different URL. It can be easily recreated. Let me know if Enpass team needs additional info and/or if I need to create a separate thread on this.