1Password integration always broken

Hello Giuseppe,

Thank you for reaching out, and please know that we sincerely understand how frustrating this situation must be. Dealing with a recurring issue is never acceptable, and we want to assure you that resolving this once and for all is our top priority.

I have personally escalated this matter directly to our development team to ensure it receives the attention it deserves. We are fully committed to getting to the root cause rather than providing a temporary fix.

In the meantime, my colleague Carl will reach out to you through the new case you opened with our service desk. He will share a booking link so we can schedule a dedicated support call with you. This will allow us to gather all the details we need about your specific environment — because while we are no longer reproducing this behaviour on our end, we believe there may be a configuration detail unique to your setup that is making all the difference.

To answer your question: you are not alone in using 1Password with Remote Desktop Manager, and we are determined to make sure this integration works reliably for you.

Thank you so much for your patience and collaboration. We truly appreciate it.

Best regards,

We do not know what to do anymore...
RDM is constantly failing with error "unable to retrieve 1password credentials".
we file a new ticket, they tipically wait a month to fix it, and one or two weeks later it stops working again...

are we the only ones using 1password with RDM?
is there any reccomandation?

Many thanks in advance to who can help us.

@giusepperobbiati
We do have the same issues over here. Just supporting your issues.
I just filed a bug report myself. Its constantly on and off since last august. Incredibly annoying and time consuming.
We are considering to switch to another solution if this is not being resolved in a stable way soon.

Kind regards
Lukas

We are considering to switch to another solution if this is not being resolved in a stable way soon.

@lschweizer

we too.

we use rdm to connect to hundreds of sessions a day, and we are loosing a lot of time because first we have to search the entry in 1password, then copy the username, then copy the password, it's a pita.

I have personally escalated this matter directly to our development team to ensure it receives the attention it deserves. We are fully committed to getting to the root cause rather than providing a temporary fix.

@Erica Poirier

Hi Erica, thanks for your answer.
Looking at release notes, it seems your development teams is more committed to implement new features rather than fix the many bugs that affect the ones that are already implemented and that have a greater impact on daily usage of the product.

hope this business choice will change in the future.

Hello @giusepperobbiati @lschweizer ,

Thank you for taking the time to meet with us today.

I am pleased to confirm that our development team has identified the root cause of the issue. The problem is related to how RDM handles the MFA prompt from 1Password, and a fix is currently being worked on.

We will keep you updated as soon as a corrected build is available.

Best regards,

Hello @Carl Marien
After the fix in 2026.2.1.2, it suddenly stopped working again today.
We are utterly tired of never knowing whether one of our most critical tools will still be working the next day.
With our renewal coming up, we are actively evaluating alternative solutions, as I’m running out of reasons to justify staying.
Kind regards
Lukas

Hello Lukas,

Thank you for letting us know, and I'm sorry to hear that the issue has returned.

I've reached out to our development team again and shared your latest feedback, including that the issue reappeared after upgrading to 2026.2.1.2. I've also emphasized the impact this is having on your daily work and the concerns you raised about the reliability of the integration.

I'll keep you informed as soon as I receive an update from the developers.

Thank you for your patience, and I appreciate you bringing this to our attention.

Best regards,

Hello Lukas,

Thank you for the additional information.

I performed some testing on my end using both the Standard and Token authentication methods, and both are working as expected in my environment.

This makes me wonder if there may be a difference in your environment, such as an SSO configuration or another setup-specific factor that could be contributing to the issue.

Could you please share some details about your environment ? In particular, it would be helpful to know how your 1Password integration is configured (e.g., whether you're using SSO or any other authentication-specific settings). This information will help our development team compare your setup with our test environment and narrow down the root cause.
Thank you for your cooperation, and I look forward to your update.

Best regards,

Hi Carl
We use Standard/Default login method, with username, password and secret key. No SSO, no Service Account.
On the 1Password side, we have automatic user provisioning via an SCIM bridge set up.
However, this shouldn't affect anything related to this case, since it's the DUO part that seems to be failing.
Did you get a chance to look at the log files sent with the support ticket?


Kind regards
Lukas

1Password integration broken again.
We have all macs installation that do not work anymore.....

everything else that uses 1password and/or Cisco DUO works perfectly, devolutions rdm completely unusable.

Ticket submitted, revert to previous versions already tried, we are not facing 2 months of issue as last time....

PasswordManagerAccess.Common.InternalErrorException: Duo: rest call to https://api-9c32200d.duosecurity.com/prompt/xxx/pre_authn/initialization?authkey=xxx&is_ipad=false failed
---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.JsonReader.ReadAndMoveToContent()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value)
at PasswordManagerAccess.Common.RestClient.DeserializeFromJson[T](String json)
at PasswordManagerAccess.Common.RestClient.MakeRequestAsync[TContent,TData](String endpoint, HttpMethod method, HttpContent content, Dictionary`2 headers, Dictionary`2 cookies, Int32 maxRedirects, Func`2 deserialize, CancellationToken cancellationToken)
Exception_EndOfInnerExceptionStack
at PasswordManagerAccess.Duo.DuoV4.GetPromptResponse(RestClient rest, String endpoint, CancellationToken cancellationToken)
at PasswordManagerAccess.Duo.DuoV4.GetDevices(String authKey, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.Duo.DuoV4.AuthenticatePrompt(HtmlDocument html, String url, Dictionary`2 cookies, MfaMethod[] otherMethods, IDuoAsyncUi ui, IRestTransport transport, ISimpleLogger logger, CancellationToken cancellationToken)
at PasswordManagerAccess.Duo.DuoV4.AuthenticateAsync(String authUrl, MfaMethod[] otherMethods, IDuoAsyncUi ui, IRestTransport transport, ISimpleLogger logger, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.AuthenticateWithDuo(SecondFactor factor, MfaMethod[] otherFactors, IAsyncUi ui, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.GetSecondFactorResult(Int32 attempt, SecondFactor factor, MfaMethod[] otherFactors, Credentials credentials, IAsyncUi ui, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.PerformSecondFactorAuthentication(Int32 attempt, SecondFactor[] factors, Credentials credentials, ClientInfo clientInfo, AesKey sessionKey, IAsyncUi ui, IAsyncSecureStorage storage, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LoginAttempt(Int32 attempt, Credentials credentials, ClientInfo clientInfo, IAsyncUi ui, IAsyncSecureStorage storage, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LogIn(Credentials credentials, ClientInfo clientInfo, IAsyncUi ui, IAsyncSecureStorage storage, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LogIn(Credentials credentials, AppInfo app, IAsyncUi ui, IAsyncSecureStorage storage, IRestTransport transport, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LogIn(Credentials credentials, AppInfo app, IAsyncUi ui, IAsyncSecureStorage storage, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Managers.OnePasswordManager.Initialize(ConnectionEngine engine, String username, String password, String accountKey, String uuid, String url, OnePasswordLoginMethod loginMethod)

Hello,

Thank you for sending over the logs. I really appreciate you taking the time to collect and share them.

I've forwarded the logs to our development team so they can continue investigating the issue. As soon as I receive any updates from them, I'll let you know.

Thank you again for your patience and cooperation.

Best regards,

Hi Carl,

Today RDM showed update to version 2026.2.4.1, in release notes there was:
Fixed 1Password authentication failing with a "Login to 1Password failed" error

I don’t know what you fixed, but the issue is exactly the same. “Unable to retrieve 1password credentials”:

Here is the application log:
AppKit.AppKitThreadAccessException: AppKit Consistency error: you are calling a method that can only be invoked from the UI thread.
at AppKit.NSApplication.EnsureUIThread()
at AppKit.NSButton..ctor()
at Devolutions.RemoteDesktopManager.PasswordManagerAccessDuo2FAViewController..ctor(DuoDevice[] devices, Boolean showRememberMe)
at Devolutions.RemoteDesktopManager.Services.UIService.ShowPasswordManagerAccessDuo2FA(DuoDevice[] devices, Boolean showUsePasscode, Boolean showRememberMe, Boolean showPhone)
at Devolutions.RemoteDesktopManager.Managers.OnePasswordUI.ShowPMADuo2FA(ConnectionEngine currentEngine, DuoDevice[] devices, Boolean showUsePasscode, Boolean showRememberMe)
at Devolutions.RemoteDesktopManager.Managers.OnePasswordUI.ChooseDuoFactor(DuoDevice[] devices, MfaMethod[] otherMethods, CancellationToken cancellationToken)
at PasswordManagerAccess.Duo.DuoV4.AuthenticatePrompt(HtmlDocument html, String url, Dictionary`2 cookies, MfaMethod[] otherMethods, IDuoAsyncUi ui, IRestTransport transport, ISimpleLogger logger, CancellationToken cancellationToken)
at PasswordManagerAccess.Duo.DuoV4.AuthenticatePrompt(HtmlDocument html, String url, Dictionary`2 cookies, MfaMethod[] otherMethods, IDuoAsyncUi ui, IRestTransport transport, ISimpleLogger logger, CancellationToken cancellationToken)
at PasswordManagerAccess.Duo.DuoV4.AuthenticateAsync(String authUrl, MfaMethod[] otherMethods, IDuoAsyncUi ui, IRestTransport transport, ISimpleLogger logger, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.AuthenticateWithDuo(SecondFactor factor, MfaMethod[] otherFactors, IAsyncUi ui, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.GetSecondFactorResult(Int32 attempt, SecondFactor factor, MfaMethod[] otherFactors, Credentials credentials, IAsyncUi ui, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.PerformSecondFactorAuthentication(Int32 attempt, SecondFactor[] factors, Credentials credentials, ClientInfo clientInfo, AesKey sessionKey, IAsyncUi ui, IAsyncSecureStorage storage, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LoginAttempt(Int32 attempt, Credentials credentials, ClientInfo clientInfo, IAsyncUi ui, IAsyncSecureStorage storage, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LogIn(Credentials credentials, ClientInfo clientInfo, IAsyncUi ui, IAsyncSecureStorage storage, RestClient rest, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LogIn(Credentials credentials, AppInfo app, IAsyncUi ui, IAsyncSecureStorage storage, IRestTransport transport, CancellationToken cancellationToken)
at PasswordManagerAccess.OnePassword.Client.LogIn(Credentials credentials, AppInfo app, IAsyncUi ui, IAsyncSecureStorage storage, CancellationToken cancellationToken)
at Devolutions.RemoteDesktopManager.Managers.OnePasswordManager.Initialize(ConnectionEngine engine, String username, String password, String accountKey, String uuid, String url, OnePasswordLoginMethod loginMethod)


RDM is still not usable.

Hello,

Thank you for the detailed logs.

The fix mentioned in the 2026.2.4.1 release notes was related to a different 1Password authentication issue. The issue you are experiencing, involving Duo MFA and the AppKit UI-thread exception, is still actively being investigated by our development team.

I understand that this is preventing you from using RDM as expected, and I will keep you informed as soon as we have an update or a fix available.

Best regards,

Hi Carl,

Can you please provide an estimated time when we will be able to use RDM again?

Thanks.

Hello Giuseppe,

I got some news from the development team after asking them to raise the priority. They should soon release a new RDM Mac version with fixes for the 1Password integration. It's a matter of a few days.

We will let you know as soon as it's available.

Best regards,

Hello Giuseppe,

I thought it would take a few days, but it was only a few hours. The development and QA teams confirmed that it is much more stable with 1Password.

Could you let me know if version 2026.2.4.4 works better on your end?

Best regards,