Allow for Private/Incognito Window as part of Devolutions Server Connection
0 vote
We have different accounts and Different SAML connections and we need the ability to authenticate with a fresh with no inherited cookies or connections for our Devolutions Server connection.
Hi,
Thank you for sending us feature request, it is always appreciated. I would like to understand more what you need. Could you give us more context on what could help you ? Are you talking about RDM or DVLS Web interface ? In RDM, a datasource is created with a specific user. So when you open a datasource, a connection will be created with that user. Cookies are not used at that moment. You should have to fill your credentials every time. If you want to use a different user, we suggest to create a duplicate of the datasource and change only the user. So it will be possible to toggle between your datasource.
Is it something that could help you ?
Best regards,
François Dubois
Sorry this was not answered. Talked to to support engineer that stated he would get you the reason but I don't see traction on this issue.
We have Multiple types of accounts to support our customers and our internal security. Because Devoutions calls a website for auth we can only use one account because of the authorization path that is done with Azure as our SAML token does not timeout on every website connection. We need to have a way to launch the data source via RDM with incognito so that we can auth to the data source with different creds that are not tied to our machine accounts. This is for security.
Hi,
When you log in to DVLS, you are redirected to Azure to enter your credentials. At that moment, azure will keep your info into the browser. That part is is out of our control. But if I understand correctly, you would like to avoid that behavior and don't want the browser to keep your azure information ? Am I correct ?
Also, when you connect to DVLS and you are forwarded to Azure, it is possible to select the account that you want to use (if you have many users logged in Azure). There are different behaviors that can happen, but usually, it is the default one. You can change it here in DVLS configuration :
Please let me know if that could help!
Best regards,
François Dubois
This would solve my issue of having to copy the login url and pasting into an incognito window. to log on to different accounts within my RDM client.
Tested this and it does not work.
The work around we are doing launch a data source with our admin account when it launches a web interface we grab the URL and put into an incognito webpage and then complete the authentication. We would like to be able to do the same thing at the data source launcher for auth.
Hello,
I'm not sure to understand what it does not work. When you want to open a datasource, it opens the browser with a specific URL. If you copy that URL in an incognito webpage and you log in in that webpage, you should be logged in RDM after that. Is it what you have seen ?
Best regards,
François Dubois
this is exactly what we have to do to use different user accounts that is why we would like the option to launch directly for the login as incognito mode instead of having to copy the url from the browser that is launched by the auth of RDM into a incognito session. Really would like the feature added and not have to keep doing the work around to authenticate for Admin users.
Hello,
Thank you for your answer. Ok, I understand your request. Just to be sure that our solution would fix your problem, what is the browser that you use ? We are analyzing the request, I will come back to you shortly.
Best regards,
François Dubois
Does not matter if it is Edge, Chrome, Brave, Opera, or Firefox we have to do the same thing to get around cached creds.
Hello,
I have added that feature request in our backlog. I can't promise it, but we will try to fit it in the next version planned in March. We will keep you posted when it will be available.
Best regards,
François Dubois