- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
04-23-2023 02:25 AM
I tested the port-forwarding on PSMP 12.6 (as well as 13.0) with Integrated (!!!) mode
It doesn't work for me 😞
I also tried PSMP not in Integrated mode, the function was operational.
Here are my settings:
/etc/opt/CARKpsmp/conf/basic_psmpserver.conf
[Main]
PSMPServerVaultFile="/etc/opt/CARKpsmp/vault/vault.ini"
PSMPServerCredFile="/etc/opt/CARKpsmp/vault/psmpappuser.cred"
PSMPServerGWCredFile="/etc/opt/CARKpsmp/vault/psmpgwuser.cred"
LogsFolder="/var/opt/CARKpsmp/logs"
LocalParmsFileFolder="/var/opt/CARKpsmp"
TempFolder="/var/opt/CARKpsmp/temp"
PSMPConfigurationSafe="PVWAConfig"
PSMPConfigurationFolder="Root"
PSMPPVConfigurationFileName="PVConfiguration.xml"
PSMPPoliciesConfigurationFileName="Policies.xml"
PSMPServerId="PSMPServer"
PSMPTempFolder="/var/opt/CARKpsmp/temp"
TunnelingServerEnable=Yes
TunnelingServerPort=55555
/etc/opt/CARKpsmp/components/components.conf
AdditionalDelimiter=%
#TargetAddressPortDelimiter=#
/etc/ssh/sshd_config
AllowTcpForwarding=local
DisableForwarding=No
On the PVWA Administration > Configuration Options > Connection Components > PSMP-SSH > Component Parameters.
TunnelingServerEnable – Yes
TunnelingServerPort – 55555
And of course, I added the "SSH Proxy" to the appropriate platform UI & Workflows "Privileged Session Management" section.
EnableSSHTunneling=Yes
TunnelingPorts=22,8080,443,25
I want to access the target servers' TCP/25 (it is an SMTP server) via tunnel. The local endpoint is 1025
I tried several combinations:
ssh -L 1025:127.0.0.1:25 "administrator%targetuser%targetserver#22#25@psmpproxy"
ssh -L 1025:127.0.0.1:55555 "administrator%targetuser%targetserver#22#25@psmpproxy"
None of them are working. It seems, that PSMP try to open the designated port on the PSMP server (?!?) instead of on the target server.
Do I use the correct syntax? If not, what it is?
Has any of you a positive experience about "port forwarding in Integrated mode"??
thanks in advance
Erno
04-25-2023 01:08 AM
Hi Nino,
Thank you very much your help, the problem solved 🙂 🙂
The configuration, what I set was fine, your advisories were fine... BUT !!!
The customer periodically ran a security script on their Linux server, which ruin these parameters 😞
AllowTcpForwarding
DisableForwarding
The proper syntax is:
ssh -L localPort:127.0.0.1:tunnelingSereverPort VaultUser@TargetUser[#TargetDomain]@TargetMachine#TargetPort#
tunneltargetPort@proxyaddress
e.g. I want to access the SMTP (TCP/25) on the TargetMachine
ssh -L 1025:127.0.0.1:55555 VaultUser@TargetUser[#TargetDomain]@TargetMachine#22#25@proxyaddress
I can check the (tunneled) connection with
telnet 127.0.0.1 1025
The other side of this TCP channel is on the TargetMachine (localhost) TCP/25
So, finally working, like a charm 🙂
04-23-2023 03:17 AM
Hi @Erno Petro,
I'm using the integrated configuration with port forwarding.
I suggest you read the article PSMP Tunnelling examples and documentations.
Right now I'm not sure but I think it's not necessary to do the modification on the PVWA side but only on the PSMP side
Test this connection string
ssh -L 1025:localhost:55555 "administrator%targetuser%targetserver#22#1025@psmpproxy"
Nino
04-23-2023 04:19 AM
Hello Nino,
Thanks your response. I think, you mean
ssh -L 1025:localhost:55555 "administrator%targetuser%targetserver#22#25@psmpproxy"
#22#25 instead of #22#1025... am I right?
I receive an error message, and the integration does not work 😞
channel 3: open failed: administratively prohibited: open failed
If I run the "legacy" syntax through a non-Integrated proxy, the result is good... 🙂
ssh -L 1025:localhost:25 "administrator%targetuser%targetserver#22#25@nonintegratedpsmpproxy"
04-24-2023 12:49 AM
Hi @Erno Petro,
What is the remote tunneling port (25 or 1025)?
Test one of two strings (for CyberArk Authentication)
ssh -L 55555:127.0.0.1:1025 administrator@targetuser@targetserver#22#1025@psmpproxy
ssh -L 55555:localhost:1025 administrator@targetuser@targetserver#22#1025@psmpproxy
Nino
04-24-2023 03:46 AM
Hi @Erno Petro,
Below is the configuration used.
From PVWA
From PSMP
Nino
04-24-2023 04:37 AM
Hello Nino,
Thank you very much the screenshots. I've already set these parameters (see the initial post)
BR
Erno
04-24-2023 05:34 AM
Hi @Erno Petro,
i I understand correctly, you also modified the basic_psmpserver.conf file.
If you added them, comment out the two lines and restart PSMP services
TunnelingServerEnable=Yes
TunnelingServerPort=55555
Another doubt I have is on the ports used, you could indicate them so as to compile the string present in the documentation.
TargetPort=22
LocalPort=5500
TunneltargetPort=?
ssh -L localPort:127.0.0.1:tunneltargetPort VaultUser@TargetUser[#TargetDomain]@TargetMachine#TargetPort# tunneltargetPort@proxyaddress
Nino
04-25-2023 01:08 AM
Hi Nino,
Thank you very much your help, the problem solved 🙂 🙂
The configuration, what I set was fine, your advisories were fine... BUT !!!
The customer periodically ran a security script on their Linux server, which ruin these parameters 😞
AllowTcpForwarding
DisableForwarding
The proper syntax is:
ssh -L localPort:127.0.0.1:tunnelingSereverPort VaultUser@TargetUser[#TargetDomain]@TargetMachine#TargetPort#
tunneltargetPort@proxyaddress
e.g. I want to access the SMTP (TCP/25) on the TargetMachine
ssh -L 1025:127.0.0.1:55555 VaultUser@TargetUser[#TargetDomain]@TargetMachine#22#25@proxyaddress
I can check the (tunneled) connection with
telnet 127.0.0.1 1025
The other side of this TCP channel is on the TargetMachine (localhost) TCP/25
So, finally working, like a charm 🙂
07-10-2025 03:57 PM
@Erno Petro - In basic_psmpserver.conf, you didnt add RemoteTunnelingServerPorts parameter ?
I will have to recheck all my setting, doing something wrong.
Looking at your Syntax and example: ssh -L localPort:127.0.0.1:tunnelingSereverPort VaultUser@TargetUser[#TargetDomain]@TargetMachine#TargetPort#
tunneltargetPort@proxyaddress
I am clear with TunnelingServerPort which is 55555 for me as well.
I am not sure about Localport and TunnelTargetport. Port 1025 that you have used. Is it the port that is being used on remote server and we dont need to add it to any config ?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

