Jump to content
Enpass Discussion Forum


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by MaxM

  1. Ditto! Similar behavior for me as well.
  2. 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.
  3. 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?
  4. @Anshu kumar, thank you for pointing this out. Let me to rephrase the question then: is there a beta of the bridged app?
  5. 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: The reason for my post was that I've subscribed for Beta program but never received a UWP beta.
  6. Is it possible to use Edge Enpass extension with Windows Desktop Enpass 6 beta? Or will it require a new extension?
  7. 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?
  8. Hi @Vikram Dabas and Enpass Development Team Any updates on adding an ability to populate more than 2 fields on a login webpage?
  9. @Anshu kumar any update? The issue continues to happen intermittently on both Nexus 7 and Nexus 6P.
  10. As of recently autofilling for Royal Bank of Canada online banking site has stopped working in Chrome. I've tried both stable version and beta version 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. and Desktop Beta v
  11. 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
  12. @Anshu kumar, the issue reoccurs after reboot. Once again, it's not happening every single time but rather once in a while.
  13. 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.
  14. @kevin.purcell you may want to share the website name so that Enpass staff can investigate in details.
  15. @edenhaus thanks :). Somehow it didn't work when I tried first time. Hence the question...
  16. 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???
  17. 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.
  18. 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.
  19. 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.exe Network Information: Direction: Inbound Source Address: Source Port: 10391 Destination Address: Destination Port: 53980 Protocol: 6 Filter Information: Filter Run-Time ID: 68036 Layer Name: Receive/Accept Layer Run-Time ID: 44 However 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.
  20. 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.
  21. 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 &shy; 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 "&shy;" (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
  22. 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.
  • Create New...