500 error upon login after upgrading Performance Management

Products

• Network Observability
• CA Performance Management

Issue/Introduction

After upgrading Performance Management to 24.3.9, a 500 error page is encountered when accessing the NetOps Portal

Environment

Upgraded Performance Management from 23.3.5 to 24.3.9

Cause

In the <InstallDir>/PerformanceCenter/DM/logs/wrapper-<date?>.log there is a message noting a bad header.

 

INFO   | jvm 1    | YYYY/MM/2DD HH:MM:0SS | Caused by: java.net.ProtocolException: ProtocolException invoking https://<portalHostname>:<port>/pc/center/webservice/sso?WSDL: Invalid header name "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'https"

Looking at the netqosportal.performance_center_proprties table there is a bad entry for priority 2 (Local Override in SsoConfig)

| Custom.Headers                          |        2 | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'https://hostname/url/; connect-src 'self' ws: wss:; img-src 'self' data:https://hostname/url/; style-src 'self' 'unsafe-inline'https://hostname/url/; base-uri 'self'; font-src 'self' file:; frame-srchttps://hostname/url/|X-Content-Type-Options: nosniff|X-XSS-Protection: 1; mode=block|Referrer-Policy: strict-origin|Feature-Policy: 'none'|Strict-Transport-Security: max-age=31536000; includeSubDomains; preload | N       | ########## | 0 |

The entries for priority 0 and 1 look correct.

Resolution

Mark the local override entry as deleted and let the remote value take precedence

1) Log into mysql:

mysql netqosportal -unetqos -p

Enter the password when prompted

2) Set the bad header to deleted:

 update performance_center_properties set deleted = 'Y' where propname='Custom.Headers' and priority=2;

3) Update the priorities:

update performance_center_properties set updatedon=unix_timestamp() where propname='Custom.Headers' and priority=1;

update performance_center_properties set updatedon=unix_timestamp() where propname='Custom.Headers' and priority=2;

4) You may need to restart the 4 portal services (not mysql):

5) After you would need to set any needed headers using the SsoConfig tool if you need specific entries, for example for embedding views in a portal, or browser views in portal.

 

Additional Information

Custom headers have been added to new pages in various upgrades.

Likely one of these changes caused this issue to appear in the later revision, where the bad header settings did not impact the previous version.