In this section:
2023.2
License Server can be configured to be FIPS compliant. See Configuring License Server to be FIPS-compliant for details.
Other Notes
- License Server 2023.2 is shipped with Apache Tomcat 9.0.82 and Java Azul Zulu OpenJDK 11.66.19-ca.
- Public API for summary of active licenses on the License Server.
- Support for deploying LSS as a StatefulSet object in Kubernetes.
2023.1
Important Notes for Upgrades
- 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 Installing the Self-deployed License Server Distribution and Deploying License Server to a Custom Tomcat Server to configure License Server to log this additional information.
Other Notes
- License Server 2023.1 is shipped with Apache Tomcat 9.0.75 and Java Azul Zulu OpenJDK 11.56.19-ca.
- Windows Server 2019 is no longer supported.
- Helm Chart for LSS (available on dockerhub).
2022.2
Important Notes of Upgrades
- 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.
Other Notes
- License Server now ships with Java 11.
- Note: When deploying License Server .war distribution to your custom Tomcat server, make sure it uses Java 11.
- Support for Windows Server 2016 has ended.
2022.1
- License Server users upgrading to 2022.1 will need to acquire new network licenses for pre-existing tools if their machine ID has changed.
- Docker and Kubernetes users can now start new containers without requiring new licenses.
- Support for authenticating using JWT Access Token for OAuth 2.0 (specifically in conjunction with PIV/CAC cards) has been added.
- Starting with LS 2022.1, the maxHttpHeaderSize attribute for the Tomcat connector is set to 16384 (16 KB)
- IP v6 is now supported
- LSS now ships with Tomcat 9.0.62
- ls.war and pstsec.war can now be run on Java 11
- Windows users can now install a Windows Service for License Server using the installLSService script provided with their install.
- Password recovery from the login screen has been removed.
2021.2
- The Parasoft End User License Agreement (EULA) must be accepted to use License Server. The admin user will be prompted to read and agree to the terms of EULA when the License Server web interface is opened for the first time. The Parasoft EULA is available at https://www.parasoft.com/license.
- License Server now ships with Tomcat 9.0.54
- Addressed log4j vulnerability CVE-2021-44228 in version 2021.2.3
2021.1
This release includes the following updates.
Updated License Server UI
The new License Server interface creates a more unified experience for users. It also introduces the v2 licensing service, which is currently in beta. The beta licensing service adds support for serving licenses in Docker environments.
Enhanced Support for OIDC
You can now specify OIDC scopes attributes and specify claims in the DTP oidc.json configuration file. This provides greater flexibility for configuring DTP to work with your OIDC provider. The usernameAttribute has been deprecated but is still supported.
Additional Updates
- Beta support for licenses in dockerized environments
- License Server now ships with Tomcat 9.0.45
- Addressed log4j vulnerability CVE-2021-44228 in version 2021.1.2
FRs and PRs
| ID | Description |
|---|---|
| LS-1389 | User removed from group does not lose license |
| LS-1414 | Use case sensitive setting when filtering licenses by username |
2020.2
- License Server can now be configured to authenticate against User Administration (pstsec) using OIDC.
- License Server can now serve license tokens when a requesting tool has been configured to borrow a token.
- The Tomcat web server shipped with License Server has been upgraded to 9.0.38.
Known Issues
Upgrading to 2020.2 on Windows changes the machine ID for the host running License Server. As a result, licenses stored and served from License Server become invalid. If License Server contains invalid licenses after upgrading, contact your Parasoft representative to obtain new licenses.
2020.1
The versioning scheme has been updated to a YYYY.release format.
License Server installation is now split across two directories:
- the app directory contains the Tomcat server, startup and shutdown scripts, and other files responsible for running License Server.
- the data directory contains configuration files, logs, and other data files.
This structure facilitates greater reliability when deploying License Server to containerized systems, such as Docker.
The License Usage API has been updated to return rejected license requests.
FRs and PRs
The following FRs and PRs were resolved in this release.
| ID | Description |
|---|---|
| LS-582 | Request for license API to return user IP addresses and list of denied license requests |
| LS-572 | License usage report: show rejected licenses |
| LS-429 | LDAP groups in LS - allow LS user to operate on LDAP groups |
5.4.3
Initial release.
The ability to delegate license requests from Parasoft tools to another instance of License Server or DTP was removed.
