Describe the bug
There is a clear bug with session recording. Once you log in to a target via ssh and session starts recording, open a new terminal and try to copy something over ssh via scp -P 35901 /home/john/mongodb-compass_1.43.0_amd64.deb john@127.0.0.1:/home/john/upload_test. Stop the session in boundary. Check the recording, there will be something like this:
Session details: "Failed".
To Reproduce
Steps to reproduce the behavior:
Run boundary controller and worker.
Add a ssh target.
SSH to the target using Boundary Client.
Open an additional terminal and try to scp some file to the target.
Stop the session from Boundary Client.
Check session recordings from Boundary Admin UI.
Expected behavior
I can see both channels - first is for scp, second - is for a terminal session and I can playback them.
Describe the bug There is a clear bug with session recording. Once you log in to a target via ssh and session starts recording, open a new terminal and try to copy something over ssh via
scp -P 35901 /home/john/mongodb-compass_1.43.0_amd64.deb john@127.0.0.1:/home/john/upload_test
. Stop the session in boundary. Check the recording, there will be something like this:Session details: "Failed".
To Reproduce Steps to reproduce the behavior:
Expected behavior I can see both channels - first is for scp, second - is for a terminal session and I can playback them.
Additional context As for storage I used Minio.