I'm curious if anyone's ever tried using Password Safe [0] in a group context with the master file stored on a shared repo.
Introducing 1Password for Teams
101–110 of 151 posts
Re: Introducing 1Password for Teams
#102... provided your team doesn't include anyone using Linux. I asked them whether they had any plans to support Linux recently and got a disappointing "no comment" type of reply. Not impressed.
Sorry you were less than impressed. We can't really discuss future plans, but we are working to mature the 1Password for Teams web client into a fully functional client that can add, edit, and delete items. The whole thing is still in beta right now, but it's definitely on our must-do list. The web client runs in Chrome, Firefox, and Opera, so Linux users will definitely be able to access it there. That's our immedia…
We're eagerly awaiting an alternative to LastPass after the recent sale. 1Password is the best on OS X, but really lags everywhere else (Win, Android), but the total lack of support on Linux (for writing) is a non-starter. It'd be great to see something, even a simple CLI app to provide basic password read/write without a GUI. The threads in AgileBits' forums referencing this topic are really depressing. Is there another way to express a "vote" for basic Linux support?
Re: Introducing 1Password for Teams
#103I had hoped AgileBits would step up their Windows offerings. I've recently bought the "real Windows application", since the Universal App doesn't allow to enter new logins (really?), only view existing ones. Unfortunately, KeePass was much more useful with its Alt-A shortcut. In 1Password I need to manually copy login data from the application, since I'm using Edge and there's obviously no plugin, yet (Edge's fault).…
I rely upon 1pw on iOS and Mac, so I was really happy with the Windows Store version of 1pw.
It is billed as a work-in-progress, but on my terribly limited HP Stream 7 tablet (Windows 10), 1Password is no less stable than any of the other apps.
I suspected that Windows development has been delayed by the need to support iOS MDM (mobile device management) for businesses. And here we are!
I also suspect that Microsoft changes in development options - particularly "Universal apps" via HTML and Javascript - moved too fast for an indie developer to follow, at least over the past 18 months.
Re: Introducing 1Password for Teams
#1041Password is great. Love it.
I have been getting excited about Universal Two-Factor auth tokens. Sure, yet another standard, but U2F seems dead-simple from user perspective, and easy for developers to add to web apps.
If we rely more upon web-browser front-ends for 1Password UX, I'd feel way more comfortable with some kind of two-factor auth for the password vaults themselves.
I have inadvertently submitted my 1pw vault password to web sites, usually because keyboard focus changed and I didn't notice. Real people will inevitably do this from time to time, even in the absence of malicious phishing.
Good luck!
Re: Introducing 1Password for Teams
#105Earlier quoted context omitted.
Specific Android issues: - The Android keyboard doesn't autofill fields - in ios I could use the share extension and it would attempt to autofill - the search is hidden behind a menu and isn't present at all in the opening screen - have to go into a category - search is broken - doesn't return a list of searched for items as the ios one does, it displays suggestions instead - if I click on a search result and go back…
Sorry to hear that you're unhappy with it. I think you'll be happy with the progress when you see the next updates. There's some work being done to modernize the interface and some of your list will be tackled by that. I would encourage you to take a look at my other comment in this particular tree of comments about Android. It might offer some perspective, not that it's an excuse but it explains things a bit more an…
Thanks for the detailed reply. I do like 1Pw - it is so very well thought out on mac and ios that I expected something similar on the android side too. Good to see it is being worked on and will hopefully become a first class app alongside your other apps.
Re: Introducing 1Password for Teams
#106Maybe I'll be the only 1Password fanboy in here. I use 1pw personally and LastPass for work (shared between team of a dozen or so technicians). To compare the two - 1pw is basically one of my favorite programs. LastPass is um... adequate? We have a lot of items in our LastPass vault and anytime we search it, add or change an item there is a 5-10 second lag. This according to LastPass support is unavoidable. Something…
Keeper Security encrypts records with individual keys. Doesn't have the 5/10 sec lag.
Re: Introducing 1Password for Teams
#1071Password is great. Love it. I have been getting excited about Universal Two-Factor auth tokens. Sure, yet another standard, but U2F seems dead-simple from user perspective, and easy for developers to add to web apps. If we rely more upon web-browser front-ends for 1Password UX, I'd feel way more comfortable with some kind of two-factor auth for the password vaults themselves. I have inadvertently submitted my 1pw va…
Thanks for your kind words! See my earlier reply to digitalchoas (https://news.ycombinator.com/item?id=10504006). :)
1Password for Teams has what we call Better Than Two-Factor™ through the use of an Account Key: https://support.1password.com/account-key/
Re: Introducing 1Password for Teams
#108Earlier quoted context omitted.
Unfortunately 1pw is absolutely terrible on Android. So I was forced to switch to Lastpass even though 1pw is generally superior because I need something that works on all my devices.
Hi! What were the issues you had with the Android application? Feedback is most certainly welcome here so we can try to focus our attention on the areas that are seeing the most sad faces from our users. Thanks! Kyle AgileBits
While you are taking feedback, I would love for 1password to be able to add ssh keys and other important security bits of info.
Re: Introducing 1Password for Teams
#109Interesting - lack of active directory integration, and lack of on-prem solution is disappointing though. Edit: since someone is apparently upset over my comment - those two features are absolutely mandatory in almost all corporate environments. If you have a comment to the contrary, feel free to share it. Don't just downvote my comment because you don't personally need the features.
Really don't want to see anyone get down voted here for having an opinion. Different opinions are what drive conversation, so, I won't ignore your concerns here. I'm not super big on the terminology, but I assume on-prem is on-premise, meaning you'd like to self-host. If I have that correct then unfortunately I can't promise anything here. I will most definitely pass this along to our team though so that they know th…
Second on the request for on-prem and AD integration.
Maybe you can explore Okta integration as possibly a faster route to AD integration.
Re: Introducing 1Password for Teams
#110Earlier quoted context omitted.
Correct - on-prem = on-premise. AD integration meaning yes, ability to tie users/groups between 1password and existing AD infrastructure. The idea there being that if a user is terminated, and their AD account is deleted/locked out, everywhere else is locked at the same time. Having to go to 20 different systems to try to clean them out is a great way to miss accounts :)
Ah, that is better. No promises (and nothing in the immediate future), but this does certainly remain in the realm of possibilities. I don't want to speak for the down-voters (I'm not one of them and I think your comment is was a valuable contribution), but when I first saw AD integration requests I assumed that people wanted AD managed Kerberos authentication to 1Password for Teams; and so imagined delegating 1Passw…
No, not delegated auth although 2 factor might be nice.
Delegated user admin/sync would be what I'm looking for. Centralized user management along with RBAC makes it much easier to set policy.