Hi,
So I can successfully setup a connection to boundary target in a remote k8s cluster via a self-managed deployment of Boundary.
I have tested multiple different targets and they all work somehow, except 1 target… Yep.. 1 Target.
I have a made a daemon process that wraps boundary locally and keeps multiple local proxies running indefinitely (mainly for ease of use since it wraps around oidc auth too). Subsequently, these start local proxies on the end-users machine with brokered credentials (ssh in this case, so I use the ssh-agent for storing the keys).
When I then try to connect to the local proxy with ssh -p @localhost, the keycheck goes through and I am authenticated via ssh. However, as soon as I connect I get disconnected.
I have checked the container via a backdoor shell and that works (via kubexec), as well as checked all profile files on the host, and they are all good.
Any suggestions?