[50] Inject does not work with IDs when using Connect server

Hello @nikolamilekic , and thank you for trying out our beta!
Thank you for drawing our attention to this issue. While it has been encountered before, I believe no formal action has been taken, as a way to try to discourage the use of the CLI with UUIDs, as opposed to names, which are more user friendly and less cryptic.
However, I definitely see how it would be extremely nice to have feature parity between Connect authentication and direct 1Password authentication, so I am going to take this up with my team.
In the meantime, can you tell us a bit more about your use case? Is being able to use the inject functionality together with IDs, when using Connect, an important feature for you right now?
Thanks once again for trying out our product. Keep the good feedback coming!

Best,
Horia

Hi @"Horia.Culea_1P",

Yes, I agree, the IDs are much more cryptic but I always use them to safeguard against changing item names.
I burned myself once when I changed the name of an item and my scripts stopped working.
On the one hand, it didn't require a lot of effort to fix, but on the other, the delay between changing the name and realizing something was broken was big enough that the failure caused some head-scratching.

One of the reasons I use op in my workflow is to prevent failures when something changes (that time it wasn't a secret but its identifier).

Right now I'm looking into migrating to a Connect server so I don't always have to type in my password to log in. Will that be eliminated with the incoming CLI integration with the main app?

Good news, the integration has been already released! Check out https://1password.community/discussion/126766/biometric-unlock-is-here#latest thread for more info. This integration indeed removes the requirement of typing the password after every half-hour of inactivity, and allows you to sign-in leveraging the biometric authentication of 1Password 8. We're looking forward to hearing your feedback on it!