Sisense Log4j Statement

We'll figure it out. I can run it fine in our test environment - was looking more at production. But I'll get with our ops team and figure it out. Thanks.

dgorman jvmConnectors is a core component for native Connectors (vs generic ODBC/JDBC/OLE/etc) so likely a good chance you are using it. I checked with the Support team and they passed this along if you are not using a WAF...If you need additional help with this you can open a ticket here: https://support.sisense.com/kb/en/contact

yy_gt  Our apologies for sharing incorrect details, we will get that updated, but that is correct. You can open a Support ticket via: https://support.sisense.com/kb/en/contact

Hello Sisense Community! Please note that we will be adding continuous updates to the attached pdf. If you have any questions, it is recommended that you reach out to your designated CSM or visit support.sisense.com to submit a support ticket. 

The documentation in the .pdf file seems fairly comprehensive for Windows deployments. Is there similar documentation available for Linux based deployments? 

tylewis29 I'll pass the word on that this was requested. The linux patch is more straightforward being command line config file updates using awk to set Dlog4j2.formatMsgNoLookups=true in relative pods, which disables the vulnerable JDNI lookup functionality.

Hi Allison,

We currently have Sisense (Version: L2021.11.0.118) deployed on Google Kubernetes Engine (GKE).  Will there be any patch/instruction available for the vulnerability for our set up?

Please note that there has been a new update added to the .pdf above.  

Logan_BaileyGP - It is recommended that you review the most recent update shared in the .pdf above and reach out to support [support.sisense.com] with any additional questions. 

Is there any instruction to apply patch for Linux2021.11 with Kubespray deployment? 

davidlin Logan_BaileyGP 

We do not have any specific instructions for GKE or Kubespray upgrade, they follow the standard instructions for deployments on Linux here: Upgrading Sisense on Linux and then referencing your correct current version of your config.yaml (eg, cluster_config.yaml, cloud_config.yaml, etc) and modifying it with the update parameter.

With any cloud deployments, you should always do a backup and run your upgrade against your non-prod environment first in addition to using snapshots for easily rollback where available. 

Backing up and Restoring Sisense 

Once upgraded in your non-prod environment, you should do a QA check of the following:

1. If you have implemented SSL, access the Sisense server from an external network, using SSL, and ensure the dashboards load as expected.
2. If you have implemented SSO, log in to Sisense using SSO, and make sure that a user can see all of their dashboards.
3. If you use any plugins or add-ons, load dashboards using plugins, and make sure they are loaded correctly.
4. If you have rebranded Sisense, check the following:
   • Rebranded emails are sent and are displayed as expected
   • Homepage and logo are displayed as expected
   • Dashboards that are embedded into your site and application are working as expected
5. If you have implemented active directory, log in to Sisense using an account from active directory and make sure your user can log in and see all of their dashboards.
6. Create a new ElastiCube and import a data source (Excel or CSV file, or any other).
7. If you have dashboards or widgets using custom scripts, load the dashboard or the widget to make sure they’re loaded correctly.
8. Run a build of an existing ElastiCube successfully.
9. Create a new dashboard, and add a Table or Pivot widget. Ensure the widget loads data.
10. If you collected information about your environment, including how many ElastiCubes, dashboards, users, and groups you have, verify that the number of assets in the upgraded deployment is correct.
11. Export a widget to Excel. Ensure the file is downloaded and has the relevant data.
12. Export a dashboard to PDF. Ensure the PDF is created and opened successfully.
13. Send a PDF report of a dashboard through Sisense and ensure it’s received.
14. Shut down one of the query nodes and verify that dashboards return the correct result.
15. Verify that ElastiCube distribution works and that the Last Build time in the Data Source section of the Admin page changes.

If you run into any issues on the non-prod upgrade, do not proceed and feel free to reach out to our Support team for assistance. If your upgrade goes fine and the above QA check went well, follow the same steps for your production deployment.