Launch RDP not working

[phil210802]

I am able to connect to SSH and Telnet sessions using Scalus, however when I try and use Scalus to connect to RDP I am prompted by SPS to enter a target server.

Please see attached.

[phil210802]

If however I download the RDP file and launch it, it works as expected.

[CodyBatt]

Please export your scalus config and post it here so we can try to reproduce with your same settings. What version of Windows are you on? Also what version of SPP is providing the URL? If you can grab the temporary rdp file mentioned in the SCALUS logs that can also help.

[phil210802]

web.config

<?xml version="1.0" encoding="utf-8"?>

[phil210802]

appsettings.json

{ "Logging": { "FileName": "scalus.log", "MinLevel": "Information", "Console": true }, "Configuration": { "FileName": "SCALUS.json" }, "Lifetime": { "IgnoreShutdown": false } }

[CodyBatt]

This is the file we need:

[phil210802]

Sorry.

Here you go.

Thanks. scalus.json

[CodyBatt]

What version of windows and what version of SPP?

[phil210802]

SPP 7.4, SPS 7.4

[phil210802]

Windows 10 22H2 (OS Build 19045.3570)

[CodyBatt]

Scalus takes the URL from SPP and parses it into properties then writes out a temporary RDP file according to one of the installed templates and launches it with RDP client.

Either:

• The parser isn't parsing the URL correctly (SCALUS bug)
• The URL has bad data (SPP bug)

• Or the template isn't correct (Configuration)

  With the full text of the URL being launched, the correct RDP file and the incorrect RDP file it should be possible to see what's going wrong and reproduce it.

Can you try again and paste here the full text of the URL being launched:

The contents of the temporary RDP file (it's just a text file):

And the contents of the working RDP file returned from SPP?

@JaredCuster

[phil210802]

@CodyBatt & @JaredCuster

Details as per request.

Thx.

scalas created rdp file.txt spp created rdp file.txt WinRdpTemplate.txt

[phil210802]

[CodyBatt]

So this is the working username:

username:s:vaultaddress~20.5.19.50%token~A5HabfCeZPZDk6h2Bo4BqyAWiB4JZvNNbfwqZHWxBjXLS8CHmJGKBy63Ag8bmWZWRtu75b2vd3VGyVg2W4%admin_1@pf1idlab.local%20.5.19.11

And this is the incorrect username. Pretty obviously has invalid characters:

username:s:pf1idlab.local\vaultaddress~20.5.19.50%token~A5KvBHRJDcscWqGXYsHSw4xynemEGEcGQeAbQcCSqa2NbGRPzkXNREPqrfWN238kXuZtyJi4mLs66LDaj9�min_1 .5.19.11:3389

Defintely looks like a scalus bug.

[JaredCuster]

@phil210802 unable reproduce, can you attach the scalus.log file please.