Troubleshooting cross launching application issues on different RSSO servers

The cross launch link is not displayed and the following error messages are displayed in the browser:

• Chrome—No text is displayed in the Iframe and the developer console in the browser (F12) displays the following message:
  Refused to display '<originating_app_host>:<port>/rsso/cross-sso?goto=<target_app_host>#jwt=<jwt_value>' in a frame because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self'".
• Firefox—Blocked by Content Security Policy.
• Microsoft Internet Explorer—This content cannot be displayed in a frame.
• Microsoft Edge—This content can’t be shown in a frame.

The target RSSO server is not configured correctly.

The proto://host:port is configured for  ALLOW-FROM Domain(s) field.

On the target Remedy SSO server, for the PREAUTH authentication option, make sure that you have entered the name of the originating RSSO server in the ALLOW-FROM Domain(s) field.

For more information, see Configuring-the-pre-authentication-mechanism.

The following error message is displayed in iframe:

 Unexpected error happened. Failed to login. Please contact the Administrator.

The wrong certificate was provided in the PREAUTH authentication type configuration for the realm of the target RSSO server.

1. Enable the debug level server logs on the target RSSO server and reproduce the issue.
2. Check the logs.
   The following statements might be displayed:
   Authentication failed. Reason: 'Could not parse certificate: java.io.IOException: java.lang.IllegalArgumentException: Input byte array has wrong 4-byte ending unit'
   Authentication failed. Reason: 'JWT signature does not match locally computed signature. JWT validity cannot be asserted and should not be trusted.'