CORS issue on Jasperserver 8.0 launched on AWS CFT

Problem statement: 

A user on JRS 8.0 on the AWS(CFT) faces a CORS issue while embedding JRS reports on the application . The application is on HTTPS protocol and same domain. In the console we see this error: VMxx:x  GET https://xxx.xx-xxx.com/jasperserver-pro/rest_v2/settings/visualizeSettings net::ERR_FAILED 200.

Resolution:

1. Firstly, we must ensure that the domainWhitelist configuration has been set right. Configuration and DEMO for v7.8+ is covered from the 12:00 min mark:

2. Upon reviewing the network tab in the HAR file, if we can see changes in the cookies and JSESSIONID, it maybe the cause of the issue here. For this, kindly review the below-attached article to make the Sticky sessions for your Application Load Balancer:

https://docs.aws.amazon.com/elasticloadbalancing/latest/application/sticky-sessions.html

 3. The user would have to test by bypassing the web application firewall (WAF) and connect directly to their load balancer. If the CORS issue is not seen again then it can be concluded that this issue was that the CORS response headers (Access-Control-Allow-Credentials, Access-Control-Allow-Origin) are not cached by default by the WAF, adding entries to the firewall configuration to allow this resolves the issue.