Getting Blank screen while accessing the Request a Jasper Snapshot Report in IDM User console
search cancel

Getting Blank screen while accessing the Request a Jasper Snapshot Report in IDM User console

book

Article ID: 194010

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

After generating a snapshot report, when attempting to request the report, we are receiving a blank page. 

 

Environment

Release : 14.X

Component : IdentityMinder(Identity Manager), Virtual Appliance

Resolution

Solution 1:

Depending on your browser settings, you may need to enable insecure content within the browser to allow the page to display.  Perform this first as a test to make sure all communication is functional.  Once confirmed, you can enable SSL for Jasper Reports. 

If using chrome, you can try to launch it this way: 

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-running-insecure-content

 

Solution 2:  

Some environments can present this issue because was not set the "Proxy Report Request" as mentioned on Solution 2, so if you continue getting the issue ensure you have configured 

the URL is written on this format :    http://<ServerName>.<domain>.com:8080/jasperserver-pro 

and the option "Proxy Report Request" checked in. This will allow the Browser read the Report request as a cross site scripting attempt.

 

Solution 3 :

In some cases, the environment has problems because Browser detect the Report objects are being loaded from a different domain as the original request (CORS )

1. try the following , test HTTP only, by login the IM using http instead https (default) as follow :

normal IM user console login :  https://<ServerName>.<domain>.com/iam/im/identityEnv/
change to  
                                                  http://<ServerName>.<domain>.com:8080/iam/im/identityEnv/

2. set the jasperserver URL this way under Report Server Connections from IM 

    http://<JaserperServerName>.<domain>.com:8080/jasperserver-pro

  Note : advise to no use the last "/" at the end of "jasperserver-pro" 
         and to use the jasperserver FQDN too.

3. once this be working correctly , you can re-try connecting IM with https and jasper http as usual to confirm is working properly the reports on this mode also .

     Or you can use jasper in https (SSL enabled) using additional information

Additional Information

When troubleshooting this issue and requesting a report from IM, you can determine if the problem is on IM or the report server by viewing the logs:

In Jasper we see this:

 [15/Jul/2024:17:43:37 +0000] "GET /jasperserver-pro/rest_v2/reports/IM/reports/Account_Details_Report/options?_=1721065414131 HTTP/1.1" 200 55
 [15/Jul/2024:17:43:37 +0000] "POST /jasperserver-pro/rest_v2/reportExecutions HTTP/1.1" 200 122
 [15/Jul/2024:17:43:37 +0000] "POST /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/exports HTTP/1.1" 200 63
 [15/Jul/2024:17:43:37 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/exports/270ce7a5-7081-43de-9c0c-357e55890d2e/status HTTP/1.1" 200 18
 [15/Jul/2024:17:43:38 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/exports/270ce7a5-7081-43de-9c0c-357e55890d2e/status HTTP/1.1" 200 18
 [15/Jul/2024:17:43:39 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/exports/270ce7a5-7081-43de-9c0c-357e55890d2e/status HTTP/1.1" 200 18
 [15/Jul/2024:17:43:41 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/exports/270ce7a5-7081-43de-9c0c-357e55890d2e/status HTTP/1.1" 200 18
 [15/Jul/2024:17:43:42 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/exports/270ce7a5-7081-43de-9c0c-357e55890d2e/status HTTP/1.1" 200 80
 [15/Jul/2024:17:43:42 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/exports/270ce7a5-7081-43de-9c0c-357e55890d2e/outputResource HTTP/1.1" 204 -
 [15/Jul/2024:17:43:42 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf HTTP/1.1" 200 372
 [15/Jul/2024:17:43:42 +0000] "GET /jasperserver-pro/rest_v2/reportExecutions/6ae89663-a50a-49d9-be44-98acf73697cf/status HTTP/1.1" 200 17

So the most important thing in the JASPER localhost_access_log

is that we see the request getting to the server:

 [15/Jul/2024:17:43:37 +0000] "GET /jasperserver-pro/rest_v2/reports/IM/reports/Account_Details_Report/options?_=1721065414131 HTTP/1.1" 200 55
 [15/Jul/2024:17:43:37 +0000] "POST /jasperserver-pro/rest_v2/reportExecutions HTTP/1.1" 200 122

Powered by Wolken Software