Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
XIII
4 years agoSuper Contributor
[13] Can the 1Password CLI replace dotenv (on Raspberry Pi)?
On my Raspberry Pi I use dotenv to store some credentials, but I don't feel comfortable storing credentials in plain text on the SD card of that machine.
Would I be able to use the 1Password CLI instead? How?
(the credentials are used by several "services" - Node.js scripts - that run automatically; preferably I only have to log in (in 1Password) once, after every boot of the Pi)
1Password Version: CLI 2.0 beta
Extension Version: n/a
OS Version: Raspberry Pi OS 5.10
15 Replies
- Sadia_A1P
1Password Team
- BackspazeDedicated Contributor
@"Sadia.Azmal_1P" I appreciate the offer for a call, but at the moment I don't think I've got much more to add than what I've already laid out in https://1password.community/discussion/comment/627903/#Comment_627903. As I've https://1password.community/discussion/comment/627857/#Comment_627857 I've held off on testing Connect while waiting for the Service Accounts to arrive. I'll get back to you when/if I think I have some useful feedback.
- XIIISuper Contributor
1Password Connect is working pretty well for me.
However, I'm quite interested in Service Accounts to prevent some pain-points, but I'm currently overloaded (work & personal), so I don't have time for a call now.
- Sadia_A1P
1Password Team
I'm Sadia, a Product Manager at 1Password, and have some news that may be interesting to both of you. I am looking for some developers and administrators that would be interested in chatting with me about a new feature our team has been working on: Service Accounts. Earlier this year, we introduced the CLI 2.0, where users can use “run” and “inject” commands to substitute secret references for secrets stored in 1Password vaults. With our new Service Account capabilities, organizations can use a separate non-user account to control and manage access to secrets without deploying additional services like Connect.
We are currently building out service accounts and want to understand your pain-points and experiences with secrets management, and gather some feedback, so we could deliver the best product for our customers.
If you are interested, please feel free to reach out to me at sadia.azmal@agilebits.com or sign-up for a 30 minute slot on Calendly. I look forward to hearing from you :)
- BackspazeDedicated Contributor
I'm running all kinds of services, scripts and other automations on my desktop and my NAS. All of those would benefit from integrating with 1Password, instead of having credentials to email accounts (and other accounts) in plain text or encrypted using a convoluted process which requires some work if I were to change a password somewhere. If I could use 1Password for this I'd only need to update the password(s) in 1Password and the scripts would just keep on running without issues.
At the moment it's just me in my family who would be using this, partly because I've not been able to get more people on board the password manager train (something I think many here can relate to) and the pandemic didn't make it any easier. But with time I expect there to be more who'll join our family account who'd want (or need) to use these kind of features. I could help them automate some thing(s) at their place and teach them how to troubleshoot when something goes wrong and put the documentation in 1Password. Then they'd have their own service account(s) to manage and could contact me if there's an issue they couldn't resolve by themselves.
My closest family are spread out in different cities and if I manage to reach my goal of getting everyone on board 1Password, then we'd be a bunch of Family Organizers, of which a smaller group work in IT in some capacity and who would benefit from being able to use 1Password for more than just storing credentials. Let's say we have some automation that requires a script to be run locally at each person's home but the script should leverage the same credentials. If the script references credentials in 1Password, then we can store those in a shared vault and edit those whenever needed without needing to update the script.
In 1Password Families you're either a member or a organizer, so either a regular user or a global admin. There's no granularity there (I wish there was), so I'm guessing creating and managing service accounts will only be possible for Family Organizers, just like for the other account types? In any case, it would be nice to automate the storing of the credentials for the service accounts somehow. Like if you create a service account, a login item gets created with it and it would either be stored in the creator's private vault by default, or there could be a modal with a question of where to store it. You could then move the login item around between vaults as you please, but, if possible, there could be a permanent link between the service account and the login item, so if you change the password for the account, the password stored in the login item gets updated automatically. Or perhaps creating a service account should work like many services handle API keys; you only get to see the credential(key) when the account is created and it's up to you if you want to store it and where, and if you need to replace it, you either generate a new credential or create a new service account and remove the old one.
- 1P_Simon
1Password Team
Appreciate it Backspaze!
I agree that you should be able to create as many service accounts as needed (whether that's at cost or not) as you should be able to adhere to the principle of least privilege.
I'd love to understand a bit better how you'd be using the service account feature in your Family account. Is this for a side-project? Are you running scripts or a server or something else? Is it just you who would be working on these automations or would other family members manage the service accounts as well?
As you said, the feature may not be relevant to all users, so I'm hoping this background from you and other users will give us insight in how and where we should deliver the functionality.
Thanks again for taking part in this Early Access round and providing us your feedback! It's tremendously valuable to us.
- BackspazeDedicated Contributor
1P_Simon Managing the service accounts using https://my.1password.com sounds great and I'd like as much granularity as possible, just as XIII mentioned.
As far as I know there's a cap at five or 20 guest accounts depending on what plan you're on, and that's a hard cap so it can't be expanded. You can however, even on the Family plan, invite more than five regular members at a cost. I'm just guessing that you'll also set some kind of limit for service accounts, if so, I'd like to see similar limits but no hard cap, so you can create as many as you need with a cost for more than five accounts or something. The reason for not setting a hard cap is for us to be able to adhere to the principle of least privilege.
There are also quite a few differences in the amount of settings available for Family plans vs Teams/Business plans so I'm guessing there will be similar limitations for configuring the service accounts on a Family plan vs a Teams/Business plan? Hopefully you can provide a decent amount of configuration options on the Family plan as well, but I know it's also a balancing act as to not overwhelm those who have no interest in these features. If it were up to me we'd be on a Teams or Business plan as I'd like to have some of the features available there but it would be next to impossible to persuade the other family members to sign up for that.
I understand that it's probably too early to be talking pricing, but I appreciate all the information you are able to provide, so we'll see if @ag_tyler has anything more to add at the moment. It all sounds very promising though and I've been planning for a while to take Secrets Automation for spin but haven't got around to it yet, so maybe I'll hold off on that and see what becomes of the service accounts.
- 1P_Simon
1Password Team
For my use case it would be great if there was even more granularity; I would like to configure a service account to have access to a single item (username & password).
Thank you! I'll let the team working on this project know about your use case. Thanks for letting us know! ❤️
- 1P_Simon
1Password Team
That's right. With service accounts, we're aiming to make the benefits of Secrets Automation available without needing to host a Connect server. As you said, there's a learning curve and setup cost to using Connect and we want to make it as easy as possible for you to get started with securing your automated processes.
What we currently have in mind would be that human accounts, service accounts and Connect servers are interchangeable.
When you useop run,op inject,op readandop item getin the beta you're currently testing, you'll already be able to use either your personal account or a Connect server (configured throughOP_CONNECT_HOSTandOP_CONNECT_TOKENenvironment variables). With the addition of service accounts, you'd be able to those at least for the same commands, for example by configuringOP_CREDENTIALenvironment variable.This interchangeability allows for a couple things:
- You can use a different authentication method depending on where your service is running. For example, you can run your application locally usingop runwith your personal account and on a webserver in production using a Connect server withop run. You could run your end-to-end tests (that require API keys to authenticate to third-party services) locally usingop runwith your personal account and in a CI/CD pipeline usingop runwith a service account credential. This allows you to re-use the script/Docker container/environment file (with https://developer.1password.com/docs/cli/secrets-environment-variables#step-3-differentiate-between-environments) achieving https://12factor.net/dev-prod-parity.
- You can get started locally using your personal account, publish to production using a service account and upgrade to a Connect server when you have the need for lower latency and/or more control.Would they be another type of account within a 1Password account that you create and manage at https://my.1password.com/ or would they be just some kind of local service accounts managed within 1Password CLI?
In our current idea, you would be able to manage service accounts using https://my.1password.com. Is this important to you? What would you like to be able to configure and manage?
If they are managed in the web portal, would they come with a cost or be free (up to a certain amount, like guest accounts) and would they be available for all kinds of 1Password accounts (Personal, Families, Teams etc)?
I have no information to share about that yet. As a developer, I'm focused on achieving your goals and adding value for you. If there's any way in which we can add more value for you, please let me know!
Maybe @ag_tyler has an update about pricing, but I believe this hasn't been evaluated yet. The project is still early stage.