Eitan

Thanks. This was the solution for my issue.

Hopfully a coockies won't be a obsticle in the upcoming version and the login process (SSO with Azure) will be simple and fast and not like today.

I would like to thank CTERRY for his help.

I've had this same issue and so has my colleague. You have to clear your cookies for *devolutions* in your default browser then authenticate again. Not sure why a desktop application would be dependent upon cookies in the browser, but it has resolved the issue every time.

Combine this with the overly complex authentication process for devolutions password hub/devolutions portal and you've got quite a frustrating experience on your hands!

While sussesfuly added to RDM the password hub business on my home PC, at work's PC, it didn't work.

Using MFA and Azure SSO on my account - work like a charm on my home's pc.

Authenticate was completed successfully, then return to RDM the error was generated:

Status: 401

Response:

Stack:

at Devolutions.Hub.Clients.HubClient.<PreLoginAsync>d__31.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Devolutions.Hub.Clients.HubClient.<<PreLogin>b__30_0>d.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at Devolutions.Hub.Clients.HubClient.PreLogin()

at Devolutions.RemoteDesktopManager.Managers.DevolutionsHubDataSourceManager.Connect(HubConnectionDataSource dataSource, String privateKeyBase64Url, Byte[] privateKeyBytes)

Any idea?

I'm have the same issue. using latest version on both products. using OTP on RoboForm with google authentication method.

any news?

Eitan