Secrets API Compliant

[schiffy91]

Hey there,

Is the 1Password team open to prioritizing compliance with Freedesktop Secrets Service API? Using 1Password to manage my SSH keys on Linux is pretty snazzy. I would love to go a step further and use it in-place of services like KWallet. A few folks were discussing this on reddit recently: https://www.reddit.com/r/kde/comments/1fmhhgf/beginner_question_do_i_need_kwallet_and_can_it_be/

[SimonBarendse]

Hi @schiffy91, we aim to keep 1Password building blocks, such as 1Password SDKs generic, so that it can be used to build a wide range of integrations and for a wide range of use cases. When integrations require more specific interfaces or integrations, as Max also noticed on Reddit, those can be build on top of the SDKs. When foundational functionality is missing in the SDKs that's required to complete the interface, we're open to feature requests for those. This strategy allows us to focus and prioritize the missing foundational functionality, while enabling an as wide as possible integration surface.

[schiffy91]

Totally makes sense. In fact, earlier today I found this, which is exactly what I was proposing (and exactly the thing you had mentioned your APIs would enable building). Going to close this out. Though I do wish there was a version of this API that routed to the locally-installed version of 1Password! Similar to how the SSH Agent works in 1Password