Jaspersoft - Load Balancer Issue

[Augustin Samraj]

Dear All

Our Clarity is on 15.4.1. and Jasper on 6.4.2

We have a (F5) load balancer configured to access Jaspersoft running on two nodes (A & B).

When nodes A and B are up, load balancer url does not work and throws the following error.

Mixed Content: The page at 'https://JASPERURL/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://JASPERURL/j_spring_security_check'. This request has been blocked; the content must be served over HTTPS.

When node A is up and B is down, load balancer works without issues

When node A is down and B is up, load balancer works without issues.

Experts, please advise.

@SumanPramanik @Nika_Hadzhikidi​​​

[Suman Pramanik]

Mixed mode i.e running clarity with http as well as https along with jaspersoft is not supported. Check your SSL setting at CSA and ensure to enable only HTTPS for clarity. Also can you try to login to Jaspersoft URL directly using superuser and see if that is working or not.

------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[Augustin Samraj]

Thanks for the response, Suman.

We have a separate load balancer (LB) for Jaspersoft. The scenario here is, I am trying to directly access the Jaspersoft LB outside of Clarity and face this issue.

Jaspersoft URLs (Node A and B) when directly accessed through superuser work well without issues. Please advise.

[Suman Pramanik]

Hi Augustin

What is the use case you are trying to do.

Regards

Suman Pramanik

------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[Augustin Samraj]

We wanted to change a stand alone Jaspersoft instance to a cluster by adding additional Jaspersoft server and balance the load through F5 load balancer to improve the overall performance of the reporting. 

This is what we wanted to do and got stuck as explained in the description of this thread.

[Augustin Samraj]

Hi Suman
Can you give some insight on this?

[Suman Pramanik]

Sorry couldn't respond earlier. I dont see anything wrong. It could the the way you created VIP pool in F2 could be an issue. Also I believe all the nodes which you installed are running HTTPS

------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[Suman Pramanik]

Yes one should be primary and other should be cluster

------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[Augustin Samraj]

Hi Suman 
Thanks for responding.

All the nodes are on http only. Is it mandatory to have all nodes in https when we have SSL enabled Load Balancer (LB) configured? If it is mandatory, it shouldn't work when either of the servers are up, right?

Today, I tried executing ./admin update jasperParameters command from clarity server, by keeping the reporting server's LB in the "Web URL"  under "Reporting" tab in CSA. It failed with below error.

"SYS 29-07 18:59:03,121 - User ppmjasperadmin not available in report server. code:401 parameter:
SYS 2019-07-29 18:59:03,121 [main] jasper.ClarityJasperAdmin User ppmjasperadmin not available in report server. code:401 parameter:
ERROR 29-07 18:59:03,122 - Login success, but Unauthorized access to <<Report URL>> with username ppmjasperadmin
ERROR 2019-07-29 18:59:03,122 [main] jasper.ClarityJasperAdmin Login success, but Unauthorized access to <<Report URL>> with username ppmjasperadmin
ERROR 29-07 18:59:03,122 - Could not login to <<Report URL>> with username ppmjasperadmin
com.ca.jasper.restAdapter.JasperException: Unauthorized access to <<Report URL>> with username ppmjasperadmin" 

I tried updating all keystore, importing the content, reinstalling csk, syncing ppm context etc by following this link but still facing the same error.
https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=766220#bm601c04ab-7a89-4fcf-bde2-bb5b8251c949


But the same command worked well when the LB url is replaced with actual reporting server's url in CSA. Does this gives you some hint on what is wrong here? Please advise.

[Suman Pramanik]

Hi Augustin

You mentioned earlier that accessing Jaspersoft URL using the LB URL causing the issue then accessing via clarity will still be the problem. Also I see your clarity URL as well as Jaspersoft URL is under same VIP pool as the fully qualified name is same 

Jaspersoft URL:  https://Jaspercom/reportservice

Also there is no requirement to have jaspersoft as https.





------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[Augustin Samraj]

Hi Suman

They are under different VIP pools. 
So, how to fix this? Has this something to do with LB configuration? Please advise.

[Suman Pramanik]

Hi Augustin

First thing, you need to confirm if Jaspersoft in load balancer without integration to PPM works or not.  because the error you mentioned definitely looks to be an issue with HTTP and HTTPS

------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------

[Augustin Samraj]

Sure Suman, Will check and update how it goes. Thanks for your support.

[Augustin Samraj]

This issue has been fixed. The root cause for this issue was an improper configuration of the load balancer - Cookie Persistence was enabled and it worked like a charm! Thanks Suman for all your support.

[Suman Pramanik]

Great news Augustin. Thanks for letting us know.

------------------------------
Thanks & Regards
Suman Pramanik
Principal Support Engineer | Customer Success & Support, Enterprise Software Division
Broadcom
------------------------------