Describe the Issue
The choco package version does not respect the cli's ability to cache a session. I'm not certain but I believe this may be due to how chocolatey creates it's shim.
While you could bypass the biometric, that doesn't work if the account has standard password auth disabled. The op signin command should be idempotent.
See https://www.1password.community/discussions/developers/op-signin-not-idempotent-windows/27081/replies/161248
To Reproduce
choco install opop signin and go through standard promptop signin and see you get the prompt again.
Expected behavior
The second op signin should just go through. The op cli supports a time limit and it should be respected.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):
- OS Name: Microsoft Windows 11 Enterprise
- OS Version: 10.0.26200 N/A Build 26200
- Application: op
- Version: v2.34.0
Additional context
Add any other context about the problem here.
Describe the Issue
The choco package version does not respect the cli's ability to cache a session. I'm not certain but I believe this may be due to how chocolatey creates it's shim.
While you could bypass the biometric, that doesn't work if the account has standard password auth disabled. The
op signincommand should be idempotent.See https://www.1password.community/discussions/developers/op-signin-not-idempotent-windows/27081/replies/161248
To Reproduce
choco install opop signinand go through standard promptop signinand see you get the prompt again.Expected behavior
The second
op signinshould just go through. Theopcli supports a time limit and it should be respected.Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):
Additional context
Add any other context about the problem here.