- #Syncing a sub valut enpass install
- #Syncing a sub valut enpass update
- #Syncing a sub valut enpass password
When designing Enpass, the team opted to request access to a specific folder so that a scenario such as the one described above doesn't occur, should a user's OAuth token become compromised-and it could happen, just as Vinod explains, you link your Dropbox account to a device owned by friend/partner/relative, granting them access to all of your folders and files. If another person has malicious intentions he could delete/copy/replace your primary vault data file. But another person in possession of access token can access the whole drive area including your primary vault.
#Syncing a sub valut enpass password
You need to set up sync on his device by yourself, with your cloud credentials at least once, as you certainly won't reveal your cloud password to him. Suppose, you were able to create two vaults on your cloud account and you want to share one of it with another person. The access to a cloud resource is controlled by OAuth tokens.
#Syncing a sub valut enpass update
This limitation which I had no clue about is just about to make my strife for securing my workplace passwords (that are currently being sent around through chats, emails and post-it's) much more cumbersome.Ĭan enpass please update us on if there are any plans on making this work in a simple way? With cloud providers like google drive or dropbox? A way to choose which folder we want to put the vault in and share it with another user should be simple enough and then to have the option of choosing a certain folder in the cloud to sync with? I honestly don't understand the explanation earlier, and it doesn't really matter either since it's possible for other password managers so it can't be impossible right? So just to be clear, Is a webdav service the only way to get around this issue? I have formerly used 1password, which I left for a plethora of reasons, however it was simple enough to keep several vaults in my dropbox storage and share the ones I wanted to with others.
#Syncing a sub valut enpass install
I just forced my entire workplace to install enpass on their computers because I was thinking of sharing a vault with them but now I realise I can't do it in any simple way like I was planning. Thanks to your feedback, I modified my config and it works ! And it works both on 6.0.0 and 6.0.3 simply because I didn't know that we could do it this way :-) I mean : using this URL, with webdav syntax (and not "dav" only) Then, to answer your second question ("why are you making it so complicated ?").
Is it possible at all or did you meant sharing with other nextcloud users? I mean for the Enpass app you'll need a username and password to connect to and a guest user don't have those.įirst : yes, Nextcloud is my next move :-) But I still don't get how you've solved it, though. I like your idea to share the vault with somebody, who is not registered as a nextcloud user. Is it possible at all or did you meant sharing with other nextcloud users? I mean for the Enpass app you'll need a username and password to connect to and a guest user don't have is anyway the best cloud solution
The vaults are still synced within my nextcloud instance and every user has its own WebDAV URL, like this: This way everyone has their own login credentials and see only its sub-folder(-s)/vault(-s) he has the rights for. Some of this vaults are shared with other nextcloud users and they've just added the appropriate shared sub-folder into their main folder "Enpass", too. I‘ve solved it the similar way. In my nextcloud account I have a folder, let's say, "Enpass" and in this folder some sub-folders for each vault: e.g. Why are you making it so complicated? Or are you sharing this vault somehow with not registered 3rd party users?
0 kommentar(er)
