(user deleted)

Feel free to close this if you wish. We solved the problem via a process of "looking harder" for the console password.

Hi Support,

A little embarrassing but we were reviewing upgrading DPS today and have realised we are unable to identify the correct console password for our installed instance. The console password was recently configured upon advice from the devolutions support team but some how it looks like it has been misplaced. We have all other credentials/encryption keys etc to the system but not the DPS console password. How can we resolve this issue so we can gain access to the console to perform upgrade?

Appreciate any advice on this.

Regards

Any ideas?

Thanks

Time on device and DVLS server are in sync to the second. The client devices are used for numerous google auth services and the others are no issue. This is a long term issue we have been having with the DVLS server auth. Yes both WebUI and RDM have same issue.

DVLS version is latest 2021.1.20.0 but all versions for last few years we have had the same issue with. Simply put the TOTP code generated is just not valid for long enough on the DVLS. The Google Auth client regens every 30 seconds but from all our testing it only works on the DVLS system for about first 10-15 seconds of that period. If we force the google auth client to regenerate the TOTP code it works as long as we use it straight away.

Any ideas on how to resolve this would be appreciated.

Regards

Jason

We have had an issue with the valid time a Google Authenticator code remains active for quite some time (we are now on the latest DPS but this issue has been going of for a couple of years). What we are finding is that if the Google Auth TOTP code is refreshed every 30 seconds on the end user device the code only works for say the first 5-15 seconds of that period. If we manually refresh to get a new code then we can generally authenticate without issue. Now I know that the first thing that comes to mind is that the time is out of sync between the DPS server and the users google auth device but its not. It also happens to all our users and setting up the Google Auth token again for a user also doesnt resolve the issue. Is there a setting to extend the period of time a TOTP code is valid for on the DPS server?

Thanks

Hi Érica

finally got those log files. Please see attached. Would be great to get this sorted. But it would also be good to get clarification on how DPS RADIUS auth is supposed to work for 2FA. Most other implementations of RADIUS for 2FA simply send the submitted username/password (which may contain 2FA code at end). In our case we need that submitted to the radius server and that will perform a push to the token for multi factor auth.

We have transitioned the team to google authenticator 2FA in the mean time but that also appears to be a little buggy with a lot of issues around timing of input of the 2FA code and a lot of tokens needing to be reset several times before they work correctly.

Thanks

Jason

upon some deeper inspection I'm not seeing the RADIUS packets hit the radius server. It looks like DPS is not even sending the request. If i press the test button in the radius setup window in DPS admin -> password server settings -> two factor -> radius it says everything is "successful" no matter what credentials I put in there. I think there might be a bug.

Hi Support,

We are looking to implement 2FA into RDM/Password server. We have an existing RADIUS based 2FA platform which works nice as it has push notification we need to use. But I'm not sure how or if DPS can pass through the authentication requests to the RADIUS server. After turning on the RADIUS 2FA setting for a test user I get prompted after the initial Authentication for the RADIUS code. Obviously this is not a standard RADIUS auth being sent (like VASCO and others use) for 2FA auth.

Do you have some documentation available or have some suggestions. Basically what we require is the initial authentication credentials are checked against AD (working now) then passed through to RADIUS server to confirm credentials (which will invoke our 2FA platform which is WatchGuard AuthPoint to send a push notification to verify access).

Any information or assistance would be appreciated.

thanks

Jason

sorry i submitted this to the wrong forum

Hi Support,

We are looking to implement 2FA into RDM/Password server. We have an existing RADIUS based 2FA platform which works nice as it has push notification we need to use. But I'm not sure how or if DPS can pass through the authentication requests to the RADIUS server. After turning on the RADIUS 2FA setting for a test user I get prompted after the initial Authentication for the RADIUS code. Obviously this is not a standard RADIUS auth being sent (like VASCO and others use) for 2FA auth.

Do you have some documentation available or have some suggestions. Basically what we require is the initial authentication credentials are checked against AD (working now) then passed through to RADIUS server to confirm credentials (which will invoke our 2FA platform which is WatchGuard AuthPoint to send a push notification to verify access).

Any information or assistance would be appreciated.

thanks

Jason

Looks like this is not one of those times :)

Thanks that's exactly what I needed.

Hi Support,

Hopefully a basic question but could you provide me an example powershell script to extract the <IP> meta information field from a session/connection? My limited powershell skills are hampering me on this one.

Thanks

Hi Devolution's team,

I was wondering if there is some documentation on the Macro/Script/Tool Report Entry?

I'd like to be able to generate a report of all sessions/entries under a parent folder of Entry Name and IP address. Do you have any suggestions how to do this with PowerShell or the Report Entry option?

Appreciate any advice.

Thanks