Release Notes 4.6.1

Release 4.6.1 introduces several new features and enhancements in NetStorm. This document provides information about the build versions, guidelines for upgrading to Build 4.6.1, and enhancements.

Version History

Upgrading to Build 4.6.1

Install 12.x Node Version

After installing or upgrading to Build 4.6.1, you need to verify that the 12.x node version is installed on your machine. If 12.x node version is not installed, update node_modules at the following path:

cd $NS_WDIR/webapps/harviewer/pagescore

To update node_modules, use the following commands:

rm -rf node_modules
npm install

Perform Data Backup

Build 4.6.1 might cause irreversible changes in the directory structure of your test assets. Therefore, you need to backup your data before upgrading and restore the data whenever required.

• Data Backup: Before upgrading to Build 4.6.1 for the first time, it is recommended to take a backup of all the test assets Use the following command for data backup:

tar -cvzf  testassets.tar.tz scripts testcases testsuites  checkprofile scenario_profiles replay_profiles ReplayAccessLogs

• Restore Data: In case, you want to downgrade Build 4.6.1 to previous versions, you can restore the backed up data using the following command:

tar -xvzf  testassets.tar.gz

Reset the Activation Key

After upgrading the build to 4.6.1 for the first time, you need to reset the activation key using the following command:

echo `nsu_two_step_encrypt 0` `nsu_two_step_encrypt 000000` > $NS_WDIR/sys/.twoStepAuth

Build 95 Enhancements

Apache Log4j2 Security Vulnerabilities related to Log4j 1.x

Applications using Log4j 1.x are only vulnerable to this attack when they use JNDI in their configuration. A separate CVE (CVE-2021-4104) has been filed for this vulnerability. To mitigate “JMSAppender.class” and JndiLookup.class classes are removed from the respective jar files.

Apache Log4j2 Security Vulnerabilities related to Log4j 2.x

Multiple vulnerabilities were found in Apache java logging library specific to log4j 2.x versions. For resolving these, we have upgraded the vulnerable versions to the latest version ie: log4j 2.17.1. To migrate this, we have upgarded all the relevent jar files to Log4j 2.17.1 version.

For further reference please check the official apache log4j security page :

https://logging.apache.org/log4j/2.x/security.html

Build 84 Enhancements

Support for Groovy Pipeline Script

Now without using the environment variable, you can access parameters value using the groovy pipeline script.

Provided a Copy and Download Option for Test Suite, Test Case and Check Profile

Added new options for copying and downloading an existing Test Suite, Test Case and Check Profile.

Check Profile and Scenario can be used across all projects and sub-projects

Earlier, you could use the check profiles and scenarios in a test case only from the project and subproject for which the test case was created. Now, you can use check profiles and scenarios from different projects and subprojects in a test case created in some other project and subproject. The check profiles and scenarios can now be used across all projects and sub-projects.

Build 80 Enhancements

Added the Option “Do not Wait for Test Completion”

A new option Do not wait for test completion is added in Jenkins. If you enable this option, Jenkins will initiate the test on NetStorm and display the test cycle and test run number in the console output log.