Skip to content

Employee (formerly Private) vault still only accessible using Private instead of Employee #225

Open

Description

@domsesol

Scenario & Reproduction Steps

I'm trying to access my Employee vault using DesktopAuth.

Actual Behavior

Connection to the 1Password server works and i can access the list of vaults.
When specifying the vault path, I noticed that I need to call the vault private instead of employee. For colleagues of mine it works with employee but not private.
Additionally, the vault's name returned by the CLI differs from the SDK. Vault's ID matches of course.

Name via CLI: Employee
Name via SDK: Private

Additionally, I noticed that the request via CLI works for both op read "op://employee/test/username" and op read "op://private/test/username".
However, the request via SDK works only for "op://private/test/username".

Here's the error message from the sdk when I try to use "op://employee/test/username":
Exception: error resolving secret reference: no vault matched the secret reference query

Code is attached.

main.py

Expected Behavior

Employee vault is accessible for all users via "op://employee/test/username".

The behavior & results of the CLI and SDK are consistent.

SDK version

0.4.0

Additional information

No response

Activity

  1. RoRoMaan commented on Sep 1, 2026

    @RoRoMaan

    I observe the same behavior in the Go SDK v0.4.1-beta.1 (via Terraform Provider v3.3.1).
    I can only reference the private vault with Private and not Employee while my colleague can only use Employee instead of Private.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions