Hi Xavier,
I use RDM with Delinea Secret server with the quickconnect bar quite often, but since the last two versions (I am currently on the latest 2024.3.12.0 64-bit) when I use the quickconnect bar to connect, I get the error:
but when I use a host record which I configure with the needed servername (also rdp proxy and same delinea secret credentials), the connection is working.
best regards
Michael
Hi Michael,
I've taken the liberty to move your post to a new thread.
I might need a bit more information to help you. What do you mean by using Delinea Secret Server with Quick Connect? You launch an RDP session with the Quick Connect bar and select a Delinea Secret Server as the credentials? And this fails with the error in your screenshot?
But a similar setup, but using a saved RDP connection instead, but referencing the same credential, works?
Best regards,
Xavier Fortin
Yes exactly
Hi,
Could you provide a bit more information on how you link your Secret Server credential to the entry when you use the Quick Connect option? At first glance, in RDM Windows, it only supports filling in username/domain/password directly, so I think I'm missing something. Are you using a connection template?
Best regards,
Xavier Fortin
Hi Xavier,
sure.
I do have a local entry template, using RDP over Delina Secret Server Proxy, using as hostname the variable $QUICK_CONNECT$ and a credential entry using the delinea credentials (lookup by name, mode as credentials).
That entry template is selected in the the quickconnect bar.
This was working fine since update to 2024.3.12.0, then it started to show the error you see in the first post.
regards
Michael
sorry, did not see that yesterday an update was released, so it worked until 2024.3.10.0
Hi Michael!
I reproduced the issue! The weirdest thing is that I do not reproduce it with SSH over Delinea Secret Server proxy.
I'm opening a ticket for this and will continue investigating the issue.
Best regards,
Xavier Fortin
great, thank you!
Hi Michael!
I found the issue and made a fix.
In the end, it had nothing to do with Delinea Secret Server, and the reason it worked with SSH for me is simply because the Delinea account I used for it did not need a machine name to function (as opposed the the RDP I used). The actual issue was with the resolving of the $QUICK_CONNECT$ variable. It would have failed with any other type of entries.
You can expect a fix for this in the next release of RDM.
Best regards,
Xavier Fortin
Nice, working after the update, thanks a lot!
best regards
Michael
Glad to hear it!
Do not hesitate to reach back if you find any other issues.
Best regards,
Xavier Fortin