Cannot launch Admin Console after applying UMP 9.0.2 Hotfix 2/20.1

Products

• DX Infrastructure Management
• NIMSOFT PROBES

Issue/Introduction

Since the UMP 9.0.2 Hotfix 1/9.0.2 Hotfix 2/20.1 were applied on the CA UIM environment, the Admin Console cannot be launched from the UMP Portal.

But it can be launched from the Primary Hub URL.

Message error:

<IP address> refused to connect 

where the IP address is from the Primary Hub

 

Cause

Environment

CA UIM 9.02/20.1

Resolution

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/unified-infrastructure-management/9-0-2/release-notes/ca-uim-9-service-pack-1.html

Admin Console Portlet Fails to Appear on UMP

Symptom:

The Admin Console portlet fails to display on the UMP when the 'X-Frame-Options' is set to 'deny'.

Solution:

Admin Console Portlet Fails to Appear in UMP

Symptom:

 

The Admin Console portlet fails to display in UMP when the X-Frame-Options are set to 'deny' or when the Content Security Policy (CSP) is set to 'none'.

Solution:

 

Add new keys Content-Security-Policy and X-Frame-Options using the wasp raw configure to enable the portlet to be working in UMP.

The keys should be added in the wasp of the CA UIM Server where the adminconsoleapp is running.

 

Follow these steps:

 

• Navigate to the wasp probe in the Admin Console.
• Select Raw Configure, webapps, adminconsoleapp, and Create New Key.
• Create the following keys:

   
•  

  Key

  : Content-Security-Policy

   

  Value

  : frame-ancestors http://<

  X

  >
•  
•  

  Key

  : X-Frame-Options

   

  Value

  : allow-from http://<

  X

  >

   

  X

   is the address that you are using to access the UMP. This can be FQDN or the IP address with the port if you are not using default port. For example, frame-ancestors http://ump-mycompany.com or frame-ancestors https://ump-location1.com:8080

  You may add multiple addresses if you use multiple addresses to access the UMP. In the following example, we use IP and FQDN for external access, and localhost for accessing from the local machine. For example, frame-ancestors http://10.1.2.3 http://ump-location1.com:8080 http://umplocalhost 
•  
• Select Update and restart the probe.

The following snapshot illustrates the two keys Content-Security-Policy and X-Frame-Options in the wasp raw configure:

    

For more information about the Content-Security-Policy frame-ancestors, see Mozilla Developer documentation.

For more information about the X-Frame-Options, see Mozilla Developer documentation.