HTML5 Gateway does not establish connection with F5 loadbalanced PSM servers

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HTML5 Gateway does not establish connection with F5 loadbalanced PSM servers

L3 Networker

Hi all,

 

I've installed and configured HTML5 Gateway based on docker in my environment (https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PAS%20INST/Install_PSM_HTML5_Docker.htm?tocpath=Installation%7CInstall%20PAS%7CInstall%20PSM%7CAdvanced%20PSM%20Implementations%7CInstall%20PSM%20HTML5%20Gateway%7C_____1)

So far, everything worked fine (including the certificate environment) and the psm connection using the HTML5 Gateway could be established.

 

Now I wanted to add loadbalancing for mutliple PSM servers with F5. Without HTML5 Gateway the connection, using RDP-files, was fine.

 

When I configure the PSM Gateway in the PVWA for the Loadbalancer IP, "docker log" outputs the following error:

 

guacd[21771]: INFO: Certificate validation failed guacd[21771]: ERROR: Error connecting to RDP server [PSMGW][14:11:33.626][[https-jsse-nio-8443-exec-26]][INFO ][c.c.p.m.t.CAPSMGWFilteredSSLSocket]: [F64E6C6842C1C2C7101BBD698FC2600D44642BC2D9FFBA768F0050DC8DAD3175] Closing socket to guacd. guacd[21771]: INFO: User "@5cc7a96e-1008-4b97-b20d-faa43634b4d1" disconnected (0 users remain) guacd[21771]: INFO: Last user of connection "$36ffccb5-a8e3-4164-a8c3-4f491bd30eb4" disconnected [PSMGW][14:11:33.627][[Thread-4806]][ERROR][o.a.g.w.GuacamoleWebSocketTunnelEndpoint]: Connection to guacd terminated abnormally: javax.net.ssl.SSLException: Socket closed guacd[323]: INFO: Connection "$36ffccb5-a8e3-4164-a8c3-4f491bd30eb4" removed.

F5 has ssl passthrough enabled with option "Performance (Layer 4)"

 

https://support.f5.com/csp/article/K14343463

 

Any suggestion to make this work?

Thanks in advance!

 

Best regards

Mad

 

 

3 REPLIES 3

L7 Applicator

You can test for certificate issues by running openssl s_client as the "psmgwuser" user and connecting to the loadbalancer address on port 3389.

L3 Networker

I fixed it with the following things:

  • use loadbalancer FQDN in PVWA "Privileged Session Management" configuration instead of IP
  • include loadbalancer FQDN in PSM server certificate
  • include loadbalancer FQDN into DNS which is accessible by HTML5 Gateway (also possible by using local hosts file but needs to be provided by container start)

L4 Transporter

For docker command:

-e IgnorePSMCertificateErrors=yes

 

  • 887 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!