Pivot to 1Password Secrets Automation and 1Password Connect?

[Windos]

Hey Chris, I saw an advert for 1Password Secrets Automation when sorting out something with my 1Password vault this morning.

I wonder, would it be worth pivoting the extension to using that (means using a JSON API and token rather than the 1P cli)

References:

• Secrets Automation
• Get started with a 1Password Secrets Automation workflow
• 1Password Connect API reference

I'm still trying to figure out the licensing on this. Secrets Automation itself is charged per token (with the first 3 being free), but I don't know if you need Teams or Business subscriptions for 1Password itself.

[cdhunt]

I've looked at the API and it would be much easier to develop against. I haven't looked into the 1Password subscription requirements. If it is restricted, that does put a damper on using Automation over the op cli.

[Windos]

So I have a family plan and have been able to set it up (though I had to use a link from the docs to get to the integrations page).

[Windos]

This... isn't going to be as widely useful as I'd hoped. I'd glossed over the "Connect Server". The API isn't direct to 1Password, it relies on you having a proxy of some description to act as the middle man.

I can see the case where this project continues as is for "normal" 1Password usage, and there's a SecretManagement.1PasswordConnect for this use case (so you can switch to it in Azure, for example.)

[cdhunt]

Confirmed with AgileBit that you need the Connect gateway. That does add a lot of complexity for using the API and sounds like it would end up being a sperate module.