(user deleted)

Apologies, I should have gone looking before I asked that question. I did find the token timeout in the Advanced server settings.

Thank you for your help.

Best,

~jake

Richard,

Thanks for the clarification. Is there a way to increase the token time beyond 1 day? Or is the only option to disconnect the data source every time in the beta?

Thanks,

~jake

Hello,

I upgraded our Devolutions Server from 2021.2.X to 2022.1.13 this morning. For the most part, the upgrade went fine but we have discovered a new behavioral change.

On version 2021.2.X when we opened RDM client to connect it would immediately send the DUO push and users could authenticate with their phone app.

On version 2022.1.13 when we open RDM client it opens up a webpage and forces us to log into Devolutions after that it sends the DUO 2FA push.

Is this an intended behavioral change? Is there a way to set it back so that the RDM client will just immediately send a DUO 2FA without having to authenticate to the web?

We would prefer for our users to have to log in with their password every time they open RDM.

Thanks,

~jake

Thank you for the information. I had to make some changes to our user accounts in Duo as well to get this working. Duo push is working now!

Is there any update on authentication with Duo Security? We are trialing Password server and Remote Desktop Manager and like the solution but we have a heavy investment in Duo security and would like to use that as our 2FA for Devolutions as well.

I added the web app in Duo and configured Duo in Password Server. The test button says it is successful but I can't apply that to a user and have it stay and work.

Thanks,

~jake

Thanks for your help. I had Devolutions Launcher installed but it was not opening sessions. I rebooted the client I was testing on and it started to work. I had rebooted it after the initial install of Launcher but there were some Windows updates pending on the client and perhaps those were an issue.

I have added a few test RDP sessions in Password manager and they do not open. When I try to open the session I get the "Opening Connection. Please Wait.." in the top right but it just goes away and nothing else happens.

I don't see any attempt being made to log in on the event log for the windows server I am trying to connect to. If I View Password on the RDP connection info in Password Server the username, domain, and password are all correct. If I try to do a regular RDP session, not in Password Server, they connect just fine.

I have set the login info on the folder containing the RDP session and am using Inherited credentials. I have attached a screenshot of the settings for the RDP session.

Can you help me determine what is going on?

Thanks!

I think the issue has to do with the VaultRunner domain account used for IIS app pool and its permissions to SQL. If I change it from only have db_datareader to db_owner on SQL server my domain account can log into the website.

I followed the steps for setting up integrated security for IIS and SQL found here https://helpserver.devolutions.net/configure_sqlpermissions.htm

I have attached screenshots of my IIS and SQL settings.

Thanks for any help

Sorry I should have said I am trying to get the trial of Password Server working.

There is no error, after I hit log in it simply just refreshes the log in page with my credentials still in the boxes. If I put in a bad password on purpose it will tell me bad password.

Thanks

I have installed the trial but when I try to log in, to the website, it just keeps me on the login page. I have tried creating both a Domain and Custom (Devolutions) admin user they both act the same.

If I put in a bad password, on purpose, it immediately tells me bad password.

Can someone provide some help with this? Thanks!

Hello,

We are very interested in Password Server and have downloaded the trail today. I am trying to follow the directions found at https://helpserver.devolutions.net/install_createrdmsinstance.htm.

I thought we needed to create 3 domain accounts VaultOwner, VaultScheduler, and VaultRunner for use in this section. Domain\VaultOwner has sysadmin rights to sql server but it can't connect to the server when I hit the "Test Server" button?

If I try to use the sa account it the test works.. So are those accounts supposed to in face just be SQL server accounts and not Domain accounts granted rights in SQL?

Thanks!

~jake