OP.exe CLI - Your Secret Key has changed. You must enter your new Secret Key to sign in.
Attempting to sign in with CLI for the first time, I am receiving the following message after entering my secret key and password:
Your Secret Key has changed. You must enter your new Secret Key to sign in.
I have verified my secret key has not changed in the GUI or web portal.
What needs to be corrected to complete a successful login?
op.exe signin .1password.com
Enter the Secret Key for at .1password.com:
Enter the password for at .1password.com:
Your Secret Key has changed. You must enter your new Secret Key to sign in.
Enter the Secret Key for at .1password.com:
[ERROR] 2021/06/15 23:35:40 Incorrect Secret Key
1Password Version: 7.7.810
Extension Version: op.exe 1.10.2
OS Version: Windows 20H2
Sync Type: Not Provided
Referrer: forum-search:Your Secret Key has changed. You must enter your new Secret Key to sign in.
Comments
-
Whoops, my formatting was interpreted as html tags and removed.
op.exe signin CompanyName.1password.com EmailAddress
Enter the Secret Key for EmailAddress at CompanyName.1password.com: Secret Key
Enter the password for EmailAddress at CompanyName.1password.com: Passphrase
Your Secret Key has changed. You must enter your new Secret Key to sign in.
Enter the Secret Key for EmailAddress at CompanyName.1password.com: Secret Key
[ERROR] 2021/06/15 23:35:40 Incorrect Secret KeyI also attempted with my.1password.com and received the same result:
Your Secret Key has changed. You must enter your new Secret Key to sign in.0 -
Thank you for the update! For confirmation, are you able to use this exact Secret Key to login to CompanyName.1password.com in a browser? I would like you to try this in a Private window, to make sure no data is already entered in the login form, and see if you are able to login there.
0 -
I was able to successfully authenticate a session from a browser via an Incognito window using the same secret key.
0 -
Hey @jusger ~
Jumping in for @ag_ana here, it looks like your company uses the
.ca
server 🇨🇦. Can you try usingop.exe signin CompanyName.1password.ca
instead?Unfortunately, our error messaging around signin appears to be misleading in this case. We'll make a note to improve on it in a future release. ref: dev/b5/op#1448
0 -
That was the solution, the ca server had to be used.
Thanks!0