Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
10/17/2023 07:42 AM
Hi,
I have a successful connection to AWS EC2-instance via port 8822.
However, when JIT task was created, account was provisioned.
It shows Connection Refused with port 22 instead of 8822.
What am I missing here to make it 8822?
10/17/2023 03:56 PM
@lonetlove : If i understand correctly your ssh port is not running on default port 22 instead it is 8822 right? I don't recall having separate configuration for mentioning port for ssh session launch other than what we mention in connection level. I believe it is something internally happening.
@NageshK : Any thoughts?
10/25/2023 06:56 PM
@lonetlove please check the customproperty35 of the endpoint. If that still has port 35, update it with 8822 and check if the launch works fine.
Thanks
Nagesh K
11/06/2023 07:53 PM
Hi NageshK,
I don't think it work. My teammate tried.
01/10/2024 02:49 AM
Any further update on this? @NageshK
01/16/2024 10:52 AM
@lonetlove : We had similar issue and we are able to fix it by making changes to endpoint CP35 to update the port and it worked. Somehow it looks like for launching SSH session saviynt looks for endpoint's customproperties 9 and 35 for IP address and Port number
01/16/2024 05:06 PM
Thanks for your help. Let me try again and update.
01/12/2024 07:56 AM
@lonetlove This should had worked. Can you please verify the config once more (please share screenshots here) and share the logs of pamms and sshgateway when the launch is failing?
Thanks
Nagesh K