Native browser not starting in CA PAM Web Portal Application

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

A CA PAM Web Portal service has been defined to listen on all possible ports by specifying a * in the mapped port, just like for RDP or SSH TCP/IP applications

The Web Portal application is configured as well to use Native Browser and to route through PAM

With such a configuration, access via this service results in the native browser never starting. A message about the browser being available in a few moments is never honored

 

Cause

This is working as designed

Contrarily to the other servers, wildcard is not supported as an option for web portal service configuration.

Please see Configure a Service to Access a Web Portal

Even though by analogy with the rest of the services it might look like this should work, it does not

Resolution

Please define explicitly a mapping between the desired target port and the local port

In the example we have seen before, a correct version of the service definition would be