Subject7 version 10.6.6 - 06/23/2026- May require support for upgrade – Subject7

v10.6.6 has been released!

For help with Subject7, please reach out to support@subject7.com

New

Added new encryption compliant with FIPS140-3 for Advanced View Commands Editor and JSON Editor tabs
Chrome driver is upgraded to version 149.0.7827.54 and supports Chrome browser version 149
Edge driver is upgraded to version 149.0.4022.62 and supports Edge browser version 149
Firefox/Gecko driver is upgraded to version 0.37.0 and supports Firefox browser version 152

Improvements

Improved dragging and dropping tests/groups in Execution Sets and Load Sets as follows:
- Dragging and dropping now works from bottom to top and vice versa, previously it was only top to bottom
- In Execution Sets, dragging a test/group will now display its name so that it's easier for the user to know which test/group is being dragged, same as in Load Sets
- Drop position corresponds better to final insert position, whereas previously it would always drop the test/group after the drop target
- In Load Sets, if multiple items are selected, only one name will appear for the dragged item (dragging is individual based on mouse click and not selection)

Fixes

Fixed an issue with creating a user from Administration > User & Group Management where previously an error would be displayed to the user but the user would still be created

Hydra
Please follow the points below if the “hydra” service is installed as a separate application (not in the main “docker-compose“ file).

Generate a secret key for FIPS encryption.
Please run the following command in the directory where the “hydra“ service is installed:

sudo docker pull <hydra_image> && docker run -it --rm -v "$(pwd)"/data/hydra:/home/subject7/data <hydra_image> bash /home/subject7/bin/generate-fips-key.sh

Where: <hydra_image> - the latest version of the “hydra“ docker image;
"$(pwd)"/data/hydra - the target directory where a file with the secret key will be generated.
Set the file path of the generated secret key to “hydra“ service.
Important! The “hydra” service should have a volume for the target directory, for example:

services ... hydra ... volumes: - ./data/hydra:/home/ssl

Please set the following property server.security.encryption.secret-key=/home/ssl/db-enc-fips.key for “hydra“ service in:
- ./conf/configserver/hydra.properties file;
  OR
- ./conf/hydra.env file (use uppercase variable names): SERVER_SECURITY_ENCRYPTION_SECRET_KEY=/home/ssl/db-enc-fips.key ;
Run Subject7 Platform upgrade.
Please run the following command in the directory where the Subject7 Platform is installed:

./subject7 upgrade

It's important to keep all services up to date.

Default Repo URL: registry.gitlab.com/subject7inc (Accessible with Tokens) or use your proxy URL

Container	Image URL	Version
activemq	$RepoURL/docker-containers/activemq:6.2.6.s7-b595	6.2.6.s7-b595
configserver	$RepoURL/configserver/configserver:1.2.5.432	1.2.5.432
grail	$RepoURL/grail/grail:1.1.5.404	1.1.5.404
hera	$RepoURL/hera/hera-service:3.3.4.1120	3.3.4.1120
hydra (optional)	$RepoURL/subject7inc/hydra/hydra:1.1.4.412	1.1.4.412
ml-worker	$RepoURL/ml-worker/ml-worker:2.1.4.361	2.1.4.361
nginx	$RepoURL/docker-containers/nginx:1.26.3.ubi9.s7-b595	1.26.3.ubi9.s7-b595
package-manager/script	$RepoURL/package-manager/package-manager:1.2.79.3	1.2.79.3
postgres	$RepoURL/docker-containers/postgres:15.17.s7-b595	15.17.s7-b595
postgres-backup	$RepoURL/docker-containers/postgres-backup:postgres-backup:15.17.s7-b595	15.17.s7-b595
proof	$RepoURL/platform/platform:proof:10.6.6.13580	10.6.6.13580
proof-worker	$RepoURL/platform/proof-worker:10.6.6.13580	10.6.6.13580
proof-worker-api	$RepoURL/platform/proof-worker-api:10.6.6.13580	10.6.6.13580
storage-service	$RepoURL/storage-service/storage:storage:2.2.4.891	storage:2.2.4.891
vault	$RepoURL/subject7inc/docker-containers/vault:1.20.3.s7-b552	1.20.3.s7-b552
webdrivers	$RepoURL/docker-containers/webdrivers:20260616.s7-b596	20260616.s7-b596
XPoint	$RepoURL/platform/xpoint:10.6.6.13580	10.6.6.13580

XPoint/Player update: Yes

Hot deploy: No

Jenkins plugin update: No

JIRA plugin update: No