parasoft/lss repository overview

⁠Quick reference

Maintained by: Parasoft⁠

Where to get help: Parasoft Documentation⁠, Parasoft Forums⁠, or Parasoft Support and Technical Services⁠

⁠What is License Server Standalone?

License Server Standalone (LSS) is a dedicated tool for managing licenses of Parasoft products. For more information see:

• Parasoft LSS documentation⁠.
• Parasoft LSS release notes⁠.

⁠How to use this image

⁠Start Parasoft License Server Standalone

Start License Server Standalone as a Docker container with command:

$ docker run --name license-server --user root:root -p 8080:8080 -p 8443:8443 -v LSS_DATA_DIR:/usr/local/parasoft/license-server/data -v /var/run/docker.sock:/var/run/docker.sock -v parasoft-volume:/mnt/parasoft -d parasoft/lss:latest

⁠Mountable Volumes

• /usr/local/parasoft/license-server/data - represents a directory with all the configuration and log files used by License Server Standalone.
• /var/run/docker.sock and /mnt/parasoft are required for the machineId to remain the same when new containers are started.

⁠Ports definitions

• -p 8080:8080 - exposes port for accessing LSS with HTTP
• -p 8443:8443 - exposes port for accessing LSS with HTTPS

⁠User definition

• user root:root - for docker image deployed on Linux the root user must be specified so that appropriate permissions could be applied

⁠Notes

Docker Desktop is not supported. If you run the Parasoft LSS container in Docker Desktop, the Parasoft machineId will be 0.

Docker Swarm–based deployments are not supported.

Upgrading docker may result in the Parasoft machineId changing.

⁠Advanced settings

⁠Overriding Tomcat configuration

Parasoft LSS runs on Tomcat. Tomcat and its configuration files are embedded in the Docker image. If you need to customize the Tomcat settings or provide your keystore or truststore, here are two ways to do it:

• Use a reverse proxy to configure ports and keystore. This eliminates the need to make changes to the default Tomcat settings and keystore in the container.

• Save your configuration files to a persistent storage directory and mount them when starting the container. The files are located in the following locations in the Parasoft LSS docker container:

  • server.xml - /usr/local/parasoft/license-server/app/tomcat/conf/server.xml
  • keystore - /usr/local/parasoft/license-server/app/tomcat/conf/.keystore
  • truststore - /usr/local/parasoft/license-server/app/jre/lib/security/cacerts

  Save these files to your persistent storage directory and mount them when starting the Parasoft LSS container by adding the following arguments:

  • -v /<persistent_storage>/.keystore:/usr/local/parasoft/license-server/app/tomcat/conf/.keystore
  • v /<persistent_storage>/server.xml:/usr/local/parasoft/license-server/app/tomcat/conf/server.xml
  • v /<persistent_storage>/cacerts:/usr/local/parasoft/license-server/app/jre/lib/security/cacerts

⁠Parasoft LSS internal variables

It is possible to inject the Parasoft LSS environment variable LSS_JAVA_OPTS into the Parasoft LSS docker container. For example:

-e LSS_JAVA_OPTS="-Dcom.parasoft.oauth2.jwks.uri=https://server.company.com:8443/auth/realms/demo/protocol/openid-connect/certs"

⁠License

You need to view and agree to the Parasoft End User License Agreement (EULA)⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses. As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

You can find additional details (e.g. configuring SSL, setting additional options) in the Deploying License Server In Docker documentation⁠