Hi there,
Currently using the following versions:
RDM for Mac - 2023.1.11.1
DVLS - 2023.1.7.0 (Has SSL Certificate for the FQN of the system)
DVLS-Recorder - 2023.1.1.0 (Has SSL Certificate for the FQDN of the system)
DVLS and Recording server are using a valid Let's Encrypt EC based certificate
My Recorder server is on a separate system and integrated into DVLS. When I connect to a session that has recording set to required and Remote, on windows it connects fine without any prompts. However on the Mac client I am always presented with invalid certificate for the recorder connection. This happens on RDP and SSH sessions I have. The certificate check tries to validate the recorder server name against the hostname of the session I am trying to connect to. If I use the Devolutions Gateway, this error does not occur on the Mac client.
Shouldn't the recorder server certificate check pull the value from the dvls server and check the certificate against that value as opposed to the unique per session host?
Example:
rec.dvls.example.com - recorder server
myrdp.example.local - RDP session
Connect to the session, the session connects, but a certificate error shows up saying "rec.dvls.example.com" does not match "myrdp.example.local".
Hello,
Thank you for reporting the issue, it appears the RDM Mac client is (incorrectly) validating the recording certificate against the remote machine instead of the recording server.
I will verify with the engineering team if they can find the source of the issue, if not, I will ask our QA team to try to replicate your environment so we can test it.
Best regards,
Richard Boisvert
Hi TheGr8Wonder,
RDM Mac 2023.2.5.1 is now available with a fix for this. Please, let us know if the issue persists.
Best regards,
Xavier Fortin