Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
linux
6 TopicsSuccessful authentication locally, 403 when executed on server.
When using the one password python library, I get the error "authentication error: http error: unexpected http status: 403 Forbidden" when running my code on a server or google colab, but it works fine when I run it on my laptop, even though the same credentials are used. Any idea about what might be going wrong? Here is the (slightly modified) code snippet: from onepassword.client import Client import asyncio import os async def get_mfa_code(): ONEPASSWORD_TOKEN = os.environ['ONEPASSWORD_TOKEN'] vault_cred = os.environ['vault_cred'] client = await Client.authenticate(auth=ONEPASSWORD_TOKEN, integration_name="My Integration Name", integration_version="v1.0.0") # Retrieve credentials from 1Password username = await client.secrets.resolve(f"{vault_cred}/username") password = await client.secrets.resolve(f"{vault_cred}/password") mfa_code = await client.secrets.resolve(f"{vault_cred}/mfa_code?attribute=otp") return username, password, mfa_code asyncio.run(get_mfa_code()) import nest_asyncio nest_asyncio.apply() asyncio.run(get_mfa_code())Solved16Views0likes1CommentSingle login in tiled-terminal session
We use 1password-cli to identify when logging into a remote machines through linux bash terminals. We now have multiple remote machines that we want to login simultaneously and perform the same (or similar) commands. Tmux (or other like terminator) are ideal for that since we can create a tiled-window, and synchronize all panes. However, currently the issues is, if we want to login onto multiple machines, I have to type the password into the GUI-pop-up from 1password once per remote machine. Is there a way to create a tiled login from a single-tmux-session with a single login? I guess it would require some persisting of the login state / environment? But it is unclear now how this is handled by the terminal. Thanks in advance. Best, Lukas12Views0likes0CommentsCannot connect connect-server to 1password from k8s
Hello. I have a problem with running 1Password operator in k8s cluster. Onepassword-connector does not connect to the server at all. First I had problems with onepassword-credentials.json being fetched by the connector-api and connector-sync containers if they were declared as: env: - name: OP_SESSION valueFrom: secretKeyRef: name: op-credentials key: 1password-credentials.json So I passed them via volumes / volumeMounts and defined the variable like this: volumes: - name: credentials secret: secretName: op-credentials (...) env: - name: OP_SESSION value: /home/opuser/.config/1password-credentials.json volumeMounts: - mountPath: /home/opuser/.config name: credentials readOnly: true Here I put my code to make it clear how I create the deployment: Gitlab Unfortunately I still can't connect to the server, and on the page: https://my.1password.com/developer-tools/infrastructure-secrets/connect/{connect_id} There is no information about the connection of my connect server, it only says "Not yet deployed" Neither the connect-api container nor the connect-sync inside the onepassword-connect pod log any errors. Only errors I have are for operator and OnePasswordItem, which is: 2025-02-17T20:31:08Z ERROR Reconciler error {"controller": "onepassworditem", "controllerGroup": "onepassword.com", "controllerKind": "OnePasswordItem", "OnePasswordItem": {"name":"example","namespace":"onepassword"}, "namespace": "onepassword", "name": "example", "reconcileID": "a1ba0a9c-7388-454e-9ce6-074cb6621e5c", "error": "Failed to retrieve item: Get \"http://onepassword-connect:8080/v1/vaults?filter=title+eq+%22Development%22\": net/http: invalid header field value for \"Authorization\""} sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler /workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:329 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem /workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:266 sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2 /workspace/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:227 Could I ask for help in finding the problem? MarPi8226Views0likes0Comments1Password CLI Docker Image Update for Vulnerabilities
I've been working on a minified Ubuntu base image with 1Password CLI pre-installed so I can use it as a base for some homelab projects. The only thing is I'm not able to resolve some of the vulnerabilities present in the final image because they are introduced by 1Password CLI's use of older versions of Golang / modules in Golang. Will the CLI be updated? Ideally it would be great for the official 1Password CLI docker image could be auto updated... As detected by Docker Scout, the latest 1Password CLI has these vulnerabilities, all of which are fixable with updates: CVE-2024-45337, CVE-2024-45338, CVE-2024-45341, CVE-2024-45336, CVE-2025-2286612Views0likes0CommentsTrouble getting document items in Kubernetes with 1P Connect Operator
Hey everyone, I'm trying to get a document out of 1P and into a k8s secret with the Connect Operator, version 1.8.1. I can get Login items but not Document items, even though there seems to be a discussion about this exact topic stating that Documents are supported as of version 1.3.0. Does anyone else have experience with this? --- apiVersion: onepassword.com/v1 kind: OnePasswordItem metadata: name: config-file-dot-yaml namespace: default spec: itemPath: "vaults/dev/items/config-file.yaml" This is the OnePasswordItem I have. The Document config-file.yaml is in the vault dev, and kubectl describe secret config-file-dot-yaml returns an event of "No items found with identifier 'config-file.yaml' " Is there any examples out there of getting the document? Thanks!42Views0likes4CommentsTrouble signing git commits from docker container
I am trying to set up a Linux dev container on my Windows machine. I am using VSCode Dev Containers which is doing some SSH magic that was able to get unsigned git commits to work. However, when I try to make signed commits, I get the following error: `error: cannot run [USER_HOME_DIRECTORY]\AppData\Local\1Password\app\8\op-ssh-sign.exe: No such file or directory` I saw this this other community post of a similar nature. I tried my best to follow along by: Set `SSH_AUTH_SOCK` environment variable; this didn't have explicit instructions for Windows Remove `[gpg "ssh"]` from `.git_config` Rebuild the docker image But doing so also did not resolve the issue, instead bringing up this new error: `error: Couldn't find key in agent?` Would someone be able to help me?26Views0likes0Comments