Jump to content
Enpass Discussion Forum

Abhishek Dewan

Enpass team member
  • Posts

    838
  • Joined

  • Days Won

    30

Posts posted by Abhishek Dewan

  1. Hi @APremiumUser

    We are glad to hear that you like using Enpass; thanks for all the support!

    Enpass does support Full-Time Windows Hello, even when you restart your device. Whether the full-time Window Hello will work on any device totally depends on the Windows itself.

    To determine the compatibility of the device to support Full-time Windows Hello (feature is only available with Enpass Store version), Enpass relies on this API provided by the Microsoft . It is the only way to distinguish whether the security keys are generated by a legit Hardware TPM. There is little Enpass can do in this case. Although for external TPM is available in the market we cannot ensure that they will support the given API.

    If your system supports Full-time Hello unlock, you will see a similar message under Windows Hello -

    image.thumb.png.641783c6187da04431be2651d937995e.png

  2. Hi @compoundbow83

    We were able to reproduce the concern reported by you, due to which the touch ID is not working for you, and Enpass is not accepting the master password on the first attempt in Mac. Our dedicated team is working on resolving it, and a patch addressing this issue will be released soon.

    Regarding having to authenticate your Pro license again after completely closing the app, kindly DM me the email address to which the license is linked and the system details on which you are facing this issue. I will then have it investigated for you.

  3. Hi @compoundbow83

    We are looking into the concerns reported by you. In the meantime, could you please share the version of the OS and also try disabling and then re-enabling the Touch ID in your Enpass Mac app to check if the issue persists? If you are getting any error, kindly share a screenshot of it as well. We appreciate your co-operation in this matter.

  4. Hi @olno

    Welcome to the Enpass Community.

    For troubleshooting purposes, please create a manual backup, then disconnect the sync from all the connected devices and set up the synchronization again. If the issue persists, please DM me the details of your Enpass app and OS version, which you are using on your iOS and Windows devices along with the WebDav demo account, its login id, password and the URL. I will then get this checked for you.

  5. Hi @cEuiUWoaXH

    Welcome to the Enpass Forums.

    If you are using Enpass version 6.8.0 on your macOS, I would suggest updating your Enpass app to the latest version 6.8.2, as updates address a lot of bug fixes and improvements to the app. If the issue persists where the outdated data from the iPhone is being put back into the data on your Mac, please create a manual backup of your data on your Mac (Ensure that you have the most recent data) and then try the below steps -

    1. Remove the iCloud synchronization from all the connected devices.
    2. While doing so, you will also get an option to 'Delete data from iCloud'. Please proceed with it.
    3. Enable the synchronization on your Mac first, then on the rest of your devices.

    As for moving data from your Mac to iOS, you can create a manual backup of your data on your Mac and then restore that file on your iOS Enpass app. Please refer to the below links for our handy guide on how to do so -

    1. Creating a manual backup
    2. Restoring backup

     

  6. Hi @compoundbow83

    Regarding unable to connect two tresors to the same account to sync data, our dedicated team is already aware of this issue and is working on resolving this bug.

    As for the Touch ID not working properly and Enpass app not recognizing the master-password for the first time, kindly create a manual backup/set up synchonization on your device and then re-install the app. After restoring your data, please enable the touch ID again. Let me know if the issue persists.

  7. Hi @Oceanwaves@Artem

    We have updated our repository location recently. A cached DNS entry might be causing this problem. A correct nslookup output should look like this:

    1. $ nslookup -type=any yum.enpass.io
    2. Server: 127.0.0.53
    3. Address: 127.0.0.53#53
    4. Non-authoritative answer:
    5. yum.enpass.io canonical name = d1qxtbrol3w4y3.cloudfront.net.

    #SI-2985

  8. Hi @celavakosa

    For troubleshooting purposes, please ensure that you have disconnected the NextCloud server before connecting this vault to OneDrive. If the issue persists, please share the below information with me and I'll have this investigated for you -

    1. The version of the Enpass app and OS you are using.
    2. Are you facing a similar issue on any other device as well?
  9. Hi @Piyush_Priyanshu

    I can certainly understand your disappointment in this matter.

    As I mentioned in my previous post, it is indeed possible to use the same cloud to sync different vaults by defining a separate path/folder for each vault via WebDav/OwnCloud. Regarding syncing multiple vaults to the same cloud account via different means like Google drive, One Drive, etc, I have shared your comments with the dedicated development team for further consideration.

     

  10. Hi @KarlKaos

    We tested the website which you mentioned and found that Enpass always autofill Username & Pin data on the login page. For troubleshooting purposes, please try the below steps once - 

     

    1. Take a note of your credentials for this webpage and then create a new login Item using autosave functionality. You can also refer to this link.
    2. If the issue persists, try using the PIN data in the password field.

     

    #SI-2974

×
×
  • Create New...