Skip to main content
Dec 3, 2021 4:48 PM UTC
Question

Deploy a 1Password Connect server on Azure

I am trying to deploy a connect server on Azure and keep getting the log message

{"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 30s), Wrapped: (failed to FindCredentialsUniqueKey), Wrapped: (failed to loadCredentialsFile), Wrapped: (LoadLocalAuthV2 failed to credentialsDataFromDisk), open /home/opuser/.op/1password-credentials.json: no such file or directory","timestamp":"2021-12-03T16:43:37.100099966Z","level":1}

I have tried using file storage (blob and file) which only works at a directory level and then I get a "this is a directory not a file " error.

I have tried various full paths on the server and nothing seems to work. The error seems to being able to correctly point to the credentials file in the docker-compose.yaml

please help


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Referrer: forum-search:https://1password.community/search?Search=azure

17 replies

Jun 29, 2022 9:53 AM UTC

Thanks @Joris_1P! The command I'm issuing is: https://.azurewebsites.net:8080/v1/vaults
I'm calling it from Power Automate, this is what the flow looks like (apologies for the lame obfuscation attempt, using the tools I had in the moment)

Jun 29, 2022 10:39 AM UTC

The command I'm issuing is: https://.azurewebsites.net:8080/v1/vaults

Looking at the screenshot, I am assuming that has your custom domain after https:// and before .azurewbesites?

  1. Does Power Automate return any error? If so, what does it return?
  2. Could you try the URL without :8080?
  3. What happens if you visit the /health route in your web browser? E.g. https://my-connect.azurewebsites.net/health

PS. I've edited your screenshot to mask it a bit better. Because Connect tokens are JSON, even sharing them partially could be problematic. I recommend revoking the current token.

Jun 30, 2022 1:14 AM UTC

Correct - that was my custom domain in the URL. And thank you for doing a better job of obfuscating my screenshot. :-)

I removed the 8080, and at least this time got an invalid bearer token error - so that means I was at least able to speak to the web app, so that's progress!

Jun 30, 2022 1:25 AM UTC

My own stuff-up with the access token there. Got it working, thank you!!!

Jun 30, 2022 6:12 AM UTC

You are welcome! Good to hear it's working now. Let me know if you run into anything else.

Joris

Jul 1, 2022 1:23 AM UTC

So, fun times discovering that using the Connect Server approach is quite manual in terms of giving access to vaults, creating a new access token each time, etc.
Any chance you've tried putting the CLI into an Azure Web App? :-)

Jul 19, 2022 5:00 PM UTC

We are working on improving the possibilities of using the 1Password CLI in these kinds of environments. As part of this, we are currently testing out a new service accounts feature in a small-scale private beta. If this is something you are interested in testing, you can sign up https://forms.gle/G1e9vib6UEQbTYb59.