Find another way to authenticate against RDM Hub than launching a web browser
Find another way to authenticate against RDM Hub than launching a web browser
1 vote
Every time RDM finds itself in another network or after a disconnect, It re-authenticates against RDM Hub by launching the default web browser and forces us to log into our RDM account. Although this is mainly painless as the web browser is already authenticated, this takes away the focus from RDM every time a network change occurs. As RDM is a tool for engineers who are working in a network and potentially purposefully change networks quite often, they find their work interrupted every time networks are switching. There must be a better way. It should be possible to reauthenticate in the background somehow or optionally, lower the requirements so that sessions are kept between network switches.
This affects, by the way, not only engineers switching networks, but everybody who is traveling by train where connections can get lost quite often.
All Comments (6)
Hi @perler
We’ll look into this issue as we’re supposed to just retry the token renewal if there’s a network issue. In the meantime, you can activate embedded browser login in the settings of your datasource, that way the focus will remain on RDM.
The setting is located in Datasource Settings -> Advanced -> Authentication Browser Mode
Let me know if we can help with anything else.
Best regards,
Luc Fauvel
I think this option isn't available in Devolution Personal Hub.
I think this option isn't available in Devolution Personal Hub.
@perler
Ah that might be the case yes, there’s also a global option that affects all datasources. It is located in File -> Settings -> Advanced -> User Interface -> Use embedded browser for login
Luc Fauvel
mh.. not really?
2ffef3e9-aebb-4349-891b-6ddf23422eae.png
Hello perler,
This is a brand new feature and requires RDM 2025.3.x
https://devolutions.net/remote-desktop-manager/download
Regards,
Min
ok, I see. Strangely, only one of our two notebooks is offering the update, the one stuck on 2025.2.x tells me that it is up to date even when I check for updates manually.