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 i...
1P_Simon
1Password Team
4 years agoThat'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 use op run, op inject, op read and op item get in the beta you're currently testing, you'll already be able to use either your personal account or a Connect server (configured through OP_CONNECT_HOST and OP_CONNECT_TOKEN environment variables). With the addition of service accounts, you'd be able to those at least for the same commands, for example by configuring OP_CREDENTIAL environment 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 using op run with your personal account and on a webserver in production using a Connect server with op run. You could run your end-to-end tests (that require API keys to authenticate to third-party services) locally using op run with your personal account and in a CI/CD pipeline using op run with 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.