PAM Web Portal Service is Blank

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

A TCP/UDP web portal service was created through the SAML 2.0 metadata import, but the web portal is blank when launched.

Environment

Privileged Access Management, all versions

Cause

When the SAML 2.0 imports the metadata from the SP, it uses the Entity ID as the service name as shown in the example below.

In this instance, the entity ID name was https://r.....net/, so the service was created with the same name. When PAM launches a web portal, it creates a temporary file for the service using the service name as the file name. Since Microsoft does not allow a : in the file name, the temporary file cannot get created and the web portal gets stuck. In the PAM client's logs.log, the following error would be seen.

2022-05-18 10:07:35 INFO  - May 18, 2022 10:07:35 AM com.ca.directory.jxplorer.viewer.HTMLTemplateDisplay setupTemplateLists
WARNING: Error initialising HTML Template file paths: java.io.IOException: The filename, directory name, or volume label syntax is incorrect     syserr [AWT-EventQueue-0]
2022-05-18 10:07:35 INFO  - May 18, 2022 10:07:35 AM com.ca.xsuite.common.util.CommonUtils logConsole
INFO: JXplorer init is done.     syserr [Thread-7]
2022-05-18 10:08:02 INFO  - May 18, 2022 10:08:02 AM com.ca.xsuite.common.util.CommonUtils logConsole
INFO: UP is up running.     syserr [Browser Thread: 57066]
2022-05-18 10:09:20 INFO  - May 18, 2022 10:09:20 AM com.ca.xsuite.common.util.CommonUtils logConsole
INFO: UP is up running.     syserr [Browser Thread: 57066]
2022-05-18 10:09:22 INFO  - java.util.concurrent.ExecutionException: java.nio.file.InvalidPathException: Illegal char <:> at index 66: C:\Program Files (x86)\CA PAM Client\temp\DefaultChromiumDir\https://r......net/_0     syserr [AWT-EventQueue-0]

Resolution

Update the service and remove the https:// in the beginning of the service name so PAM can create the temporary file. Then the web portal will be able to load.