Unable to retrieve 1Password Credentials

Hello,

Thank you for contacting us on that matter.

You are correct, this issue is related to an update 1Password made on their API. Our engineering team is currently working on a fix to solve this problem.

I will update the thread when progress is made on the case.

Best regards,

Hello,

I can confirm that I've got the same issue as well, even it has been fixed a few weeks ago with version 2021.2.27.0. Now the problem reappeared.



Thank you!

Best regards,
Karl

Hello Karl,

This should be fixed if you updated to RDM 2021.2.28.0. Let us know if you still encounter the issue after updating.

Regards,

Hi Hubert,

Thank you for mentioning RDM 2021.2.28.0. I just downloaded and installed this version (without uninstalling the previous version before) and it is working. RDM successfully grabs the 1Password credentials now again.

Thank you!

Best regards,
Karl

No problem, glad this works for you!

Regards,

This was fixed for a while in 2021.2.28, however, the issue has popped up yet again (perhaps another change on the 1password side) between last Friday to today.

Hello,

Yes indeed, it's broken again. I was able to use RDM yesterday afternoon (CET time) without issues as far as I can remember. But I just tested it now, and it's again with the "Unable to retrieve 1Password credentials".

Best regards,
Karl

Hello,

Our engineering department is currently looking at the 1Password issue.

Thank you for reporting.

Best regards,

All,

This appears to be resolved in latest release: 2021.2.29 (Feb 2nd release)

• Added more robustness to the 1Password integration

Hi all,

I can confirm, the bug is gone on version 2021.2.29.0. I just updated to this version right now and RDM seems to get the 1Password credentials again without problems.

Thank you!

Best regards,
Karl

Hello Together,

i have a issue with the Version 2022.1.4.0

Unable to retrieve 1Password credentials.

It don´t works on my two MacBooks the same Version number.

Hello Markus,

Thank you for your message. I did some tests internally, and I believe I was able to replicate the issue you are experiencing. I will open a ticket so our engineering team can investigate this problem.

We will keep you updated as progress is made on the case!

Best regards,

Hello Gabriel,
Update, i have found the error. I don´t have activate our Proxy Server in Network.

Now, it works very fine. Thanks for support.

Regards,
Markus

Do you know if they made another change to their API?

Just this morning I started to get this error. According to "check for updates" I was on the latest version, 2025.13.1. But if I download from the website I see 2025.14.0 is available. After updating to that I still get the error though.

Do you know if they made another change to their API?

Just this morning I started to get this error. According to "check for updates" I was on the latest version, 2025.13.1. But if I download from the website I see 2025.14.0 is available. After updating to that I still get the error though.

@licensing5

Hmm. I'm on 2025.1.41.0 64-bit , think the latest is 2025.2.14.0. I don't have the error on 2025.1.41.0. I'll update here later and try. However, given I'm (in theory) on an older version than you and i just opened and RDM session that used creds from 1password, its hard to say.

Yeah updated to 2025.2.14.0 64-bit (JIT) which did require a DB update - but no issues, I'm able to use creds from 1password for sessions.

Hmm, now I downgraded to 2024.3.31.0 and it's back to working. I'll call it good on my end and just wait a version or two before I update to 2025 again.

By the way, thank you for helping!

Hello,

Thank you for reaching out to us regarding this matter.

Could you please send us the application logs after the error occurs? This will help us investigate the issue further.

Best regards,