Search the Community
Showing results for tags 'microsoft'.
Guys good feature for future will be if we can add 2FA into Enpass for Microsoft Accounts. Now is this last one my account where I must using Microsoft Autenticator, because this is my last one 2FA which Enpass not support. Ps, two years back I used for 2FA only Microsoft Autenticator with cloud save. But as Enpass released this feature directly into Enpass so I start migrate and now I miss this last one. So I hold Enpass team fingers for some solution (Microsoft Account with 2FA + Enpass).
I am testing a trial of Enpass Business for my company of about 50 users. Our vaults are integrated into Sharepoint OnlineTeams and divided by Team Sites according to our organizational chart. All configured in a simple way but I have some doubts about the cloud sync interval between desktop clients: according to the extract of this article synchronization should work with these triggers. Every time the app is unlocked Every 15 seconds when the app is active in the foreground on your device Within 5 seconds every time you save a change The synchronization takes place only in the first case (not every 15 seconds) but if we have two clients open and we make a change, even after several minutes it does not synchronize unless we do it manually or after locking and unlocking the app. Instead, the mobile app (iPhone) syncs instantly immediately after a change made from a desktop but not vice versa. Any suggestions? Thank you!
I just did the update, and Enpass refuses to start. I am greeted with "Enpass Password Manager is currently not available in your account. Make sure you are signed in to the Store and try again. Here’s the error code, in case you need it: 0x803F8001" Having all my passwords in Enpass, it is a major annoyance. I am, of course, signed-in to the Microsoft Store. It used to work fine before the update. Please help
Hi guys, As we have mentioned in our blog-post that Edge browser extension will not be part of stable releases. We will keep the beta-stream of Traditional Windows as updated as stable stream with an additional, most in-demand feature: Edge Browser extension. The newly released Enpass Beta 5.3.1 is similar to stable Enpass 5.3.0. You can download the Edge supported Beta version from here and Edge extension from here & follow the steps mentioned in readme.txt . Before using the beta version, you should be aware of risks involved by: Disabling isolation of Edge browser: To strike down the Issue of Microsoft Edge browser (where being a UWP App, it doesn't allow any other App to connect to it on same machine through loopback), we have to disable the network isolation of Edge using the following command. CheckNetIsolation LoopbackExempt -a -n="Microsoft.MicrosoftEdge_8wekyb3d8bbwe" Warning: As per Microsoft, the use of above command to overrule the Network capabilities of Edge browser is not a general practice and is not recommended for normal users as it can make the Edge browser vulnerable. Format of Websocket origin: When edge extension connects to Enpass app via websocket, the websocket origin set by Edge is in somewhat a non-standard format https://EnpassPasswordManager_nt7fcssrybz1j:0. Ideally it should be ms-browser-extension://EnpassPasswordManager_nt7fcssrybz1j:0 Being in the https protocol format, it might lead an attacker to run an attack site on a machine that resolves to our extension ID by DNS spoofing and installing its self-signed root certificate authority on your computer. If a request come from Edge browser runing that attack site will look like an authentic request to Enpass. If you PC is already in so much control of a bad guy that he can install self signed root certificate and run a site on your machine (which requires administrator permission), you are already at potential risk. Although it is not so easy for anyone in a control environment, but as a user of Enpass, we want you to be aware of this issue. Keep using Enpass and stay secure!