...
In certain AWS or Azure Windows Server 2025 environments, the machineId may change after upgrading. If this happens, you will need to acquire a new license for License Server and will need to acquire new network licenses for pre-existing tools.
Enhancements
License Server Enhancements
- Added the ability to export and import filters and reservations from one license to another.
Improved Error Handling and Security
- Updated the default error handling behavior to prevent exposure of sensitive information.
- Replaced the default Apache Tomcat error page, which could display stack traces and version details.
Software Shipped with License Server
...
- Apache Tomcat: 10.1.54
- Java Azul OpenJDK 17.0.18+8 (17.64.17)
2025.2
Enhancements
Technical Support Archive Improvements
- Users can specify a time range (log files modified within last x days) when creating an archive.
License Server Enhancements
- New setting: Restrict access to automation licenses. When enabled, License Server will deny access to licenses with automation features unless those features are explicitly requested. This setting is enabled by default.
- Starting with version 2025.2, automation licenses will be granted only to tools that explicitly request the automation feature. This prevents desktop instances from consuming tokens intended for automation use. Both the Parasoft tool and License Server must be version 2025.2 or later and Restrict access to automation licenses setting must be enabled for this behavior to take effect.
- Contributing Developers Usage Data: License Server now captures and displays additional information about the author of the latest commit in the git repository
- New setting: Delete Contributing Developers Usage Data older than one year. When enabled, License Server will automatically delete usage data sent from Parasoft C/C++test CT and Parasoft C/C++test Standard after one year. This setting is enabled by default.
- In addition, the License Server setting Grant license token to login username is now enabled by default in new installations. Users upgrading to 2025.2 will have their current setting preserved.
- Floating licenses have been relabeled as "concurrent" licenses. No functionality has changed.
- Updated
licenseserver/usageAPI to support filtering license usage by license.
...
- Upgraded to spring-security 6.5.9 to address CVE-2026-22732
- Upgraded to tomcat 10.1.52 to address CVE-2025-66614
2025.1
Enhancements
Support for Jtest Unit Test Bulk Creation Tiers
...
License Server 2024.2 requires Java 17 and Tomcat 10.1.x. If you have installed a previous version of the License Server web archive distribution (WAR), you will need to upgrade your Java and Tomcat installations then follow the directions described in Upgrading Web Archive Distribution with a New Version of Tomcat in order to upgrade to License Server 2024.2 and retain your data and settings.
Enhancements
License Server Enhancements
- Tool licenses can now be released to the user's login username instead of their OS username. See Configuring License Server for information about enabling this option.
- Both the user's login and OS usernames are logged when a tool requests a license.
- Multiple named-user licenses can now be assigned to the same username. See Types of Licenses for more information.
- The API Documentation and Usage API Documentation pages have been separated and are now available from the Help menu.
- GET /tokens API, which returns a list of license tokens, is now exposed as a public API.
- Added GET /usage API, which allows grouping tool usage results by tool version, user, and host. See Viewing Tool License Usage for more information.
- Added ability to request tool licenses from Tool Licenses page. See Managing Tool Licenses for more information.
...
- Upgraded to tomcat 10.1.54 to address CVE-2026-29145
2024.1
Enhancements
- License Server can be configured to require tools to authenticate when requesting a license.
- You can add a descriptive tag to a license in License Server Administration, making it easier to identify and differentiate one license from another.
...
- User-Locked licenses have been renamed to Named-User licenses to match the EULA.
- Usernames are now logged when bad credentials are used to login.
2023.2
Enhancements
License Server can be configured to be FIPS compliant. See Configuring License Server in FIPS-Compliant Environment for details.
...
- Deployment in Kubernetes environments has been simplified. These changes affect the machineId. As a result, users upgrading License Server from 2022.1 or 2022.2 to 2023.1 will need to acquire new network licenses for pre-existing tools.
- License Server users will need to acquire new network licenses for pre-existing tools.
Enhancements
- For fresh installs, License Server will capture additional information, such as user identity and session ID, in log files. This is necessary for some users to be in compliance with certain regulations. Users who are upgrading should see Deploying License Server and Deploying Web Archive License Server Distribution to a Custom Tomcat Server to configure License Server to log this additional information.
...
- Deployment in Kubernetes environments has been simplified. These changes affect the machineId. As a result, users upgrading License Server from 2022.1 to 2022.2 will need to acquire new network licenses for pre-existing tools.
- License Server users will need to acquire new network licenses for pre-existing tools.
Enhancements
- Updated UI in License Server. See License Server for more information.
- Updated Permissions UI in User Administration. See User Administration for more information.
...