Unable to launch AD Dashboard in WebUI

Hello,

Thank you for reaching out!

My name is William and I'm here to assist you in any way I can.

Since you also confirmed the user can launch RDP sessions through the web interface with the Gateway, I also do not think this is a licensing issue. That is why I would like to confirm the configuration of the AD Dashboard entry.

Would it be possible to send us a screenshot of the VPN/Tunnel/Gateway configuration of the AD Dashboard entry? We want to make sure the right Gateway is configured on the entry:


Please don't hesitate to reach out if you have any questions or need further clarification.

Best regards,

Hi William,

Thanks for assisting with this. Yes, the VPN/Tunnel property of the entry is set to always connect via Devolutions Gateway, as per the documentation I referenced in the original post. The check health button also returns a successful test.

Are you able to reproduce the issue?

Joe

Hello,

Unfortunately, I'm unable to reproduce the issue.

Would it be possible to confirm that an admin can launch the session through the web interface?

Best regards,

Hello Joe,

Thank you for the update.

Even though this does not appear to be a licensing issue, I would like to review the configuration from the top to make sure nothing is being overlooked.

Could you please confirm the following for the affected user:

1. License
Make sure the user has a license that includes Devolutions Gateway access.
This is likely already the case since the user can use the Gateway with other entries, but it is still worth confirming.

2. Vault access
Ensure the user has access to the vault where the AD Dashboard entry is stored.
Since the user can see the entry and send it to RDM, this should already be correct.

3. Entry permissions
Please verify that the user has the following permissions on the entry:

• View
• Connect (Execute)
• View Password (required to launch the session through the web interface)

If everything above is confirmed, we can continue investigating further.

Best regards,

Hi William,

Thanks for the tip on the permissions, adding the 'View Password' permission resolved the issue. Is there a reason web UI requires this whereas RDM does not? Also, could the documentation be updated to include this requirement please, as its not inherently obvious when the connection is not configured with a password, or uses one from a user vault to which permission would already exist.

Joe

Hello,

Yes, the View Password permission is required intentionally. This is to avoid creating a false sense of security, since the password could still be accessed by a user through the browser’s developer console.

I will also notify our documentation team, so the documentation can be updated accordingly.

Best regards,