Subject7 version 10.6.3 - 05/12/2026- May require support for upgrade – Subject7

v10.6.3 has been released!

Improvements

Improved performance when editing Execution Sets where previously this would consume a lot of time
Improved hover behavior for the user menu to reduce accidental popups
Improved error handling when creating duplicate folders in Execution Sets

Fixes

Fixed an issue where an error would sometimes be displayed when using Test Connection inside Rest API connection if OAuth 2.0 authentication is used
Fixed an issue when using Subject7 Recorder with Custom Store Option enabled where Handler Index would capture an incorrect value on Switch_Window command

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

On-Premise Configurations (PLEASE CHECK NOTES SECTION BELOW THE TABLE)

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.5.s7-b535	6.2.5.s7-b535
configserver	$RepoURL/configserver/configserver:1.2.2.417	1.2.2.417
grail	$RepoURL/grail/grail:1.1.2.370	1.1.2.370
hera	$RepoURL/hera/hera-service:3.3.1.1097	3.3.1.1097
hydra (optional)	$RepoURL/subject7inc/hydra/hydra:1.1.1.366	1.1.1.366
ml-worker	$RepoURL/ml-worker/ml-worker:2.1.1.345	2.1.1.345
nginx	$RepoURL/docker-containers/nginx:1.24.0.ubi9.s7-b535	1.24.0.ubi9.s7-b535
package-manager/script	$RepoURL/package-manager/package-manager:1.2.76	1.2.76
postgres	$RepoURL/docker-containers/postgres:15.17.s7-b535	15.17.s7-b535
postgres-backup	$RepoURL/docker-containers/postgres-backup:postgres-backup:15.17.s7-b535	15.17.s7-b535
proof	$RepoURL/platform/platform:proof:10.6.3.13101	10.6.3.13101
proof-worker	$RepoURL/platform/proof-worker:10.6.3.13101	10.6.3.13101
proof-worker-api	$RepoURL/platform/proof-worker-api:10.6.3.13101	10.6.3.13101
storage-service	$RepoURL/storage-service/storage:2.2.1.873	2.2.1.873
webdrivers	$RepoURL/docker-containers/webdrivers:20260511.s7-b545	20260511.s7-b545
XPoint	$RepoURL/platform/xpoint:10.6.3.13101	10.6.3.13101

XPoint/Player update: Yes

Hot deploy: No

Jenkins plugin update: No

JIRA plugin update: No

Important notes:

In this 10.6.3 release version, database migration will take some time. Please set flag account.database.update.onstart=true and wait patiently until deployment finishes and server starts.

Hydra:
If Hydra is not currently installed, then you can skip its installation, including Vault Credentials.
- Automatic Upgrade Behavior
  - Please update the Hydra image value in docker-compose.yml to be registry.gitlab.com/subject7inc/hydra/hydra:1.1.1.366
    This value in the Hydra section should look as follows:

hydra:
    container_name: hydra
    image: "http://registry.gitlab.com/subject7inc/hydra/hydra:1.1.1.366"
    hostname: hydra
    domainname: hydra
    ports:
      - "8443:8443"

If Hydra service is already defined in your main docker-compose.yml, the Package Manager tool will automatically upgrade both:
- S7 Platform instance;
- Hydra service
Manual Setup (New Hydra Installation)
The manual installation steps only apply in case where a Hydra installation needs to be added to the instance.
- If Hydra service is not defined in your docker-compose.yml, follow these steps:
  1. Install Hydra
    - Deploy Hydra service on the same host as the Subject7 Platform;
  2. Update Docker Image
    - Use the latest Hydra Docker image and set it in either:
      - .env
        OR
      - docker-compose.yml
        (depending on your setup);
  3. Configure Vault Credentials
    - Add the following properties to the Hydra service:
      
      spring.cloud.vault.app-role.role-id=<role_id>
      spring.cloud.vault.app-role.secret-id=<secret_id>
    - You can add them in one of the following files:
      - ./conf/configserver/hydra.properties
        OR
      - ./conf/hydra.env
        (use uppercase variable names): SPRING_CLOUD_VAULT_APP_ROLE_ROLE_ID=<role_id> and SPRING_CLOUD_VAULT_APP_ROLE_SECRET_ID=<secret_id>;
    - Retrieve Credentials
      - Run the following command to obtain <role_id> and <secret_id>:
        
        ./subject7 gs hydra/vault
        
        Important Notes:
        <role_id> is rotated on every S7 Platform upgrade;
        <secret_id> is rotated each time the command is executed;
        You must update both values after every platform upgrade;
  4. Remove Deprecated ActiveMQ Properties
    - If present, remove the following properties from Hydra configuration:
      - spring.activemq.user;
      - spring.activemq.password;
      - spring.activemq.jmx.username;
      - spring.activemq.jmx.password;
      Check both:
      - ./conf/configserver/hydra.properties;
      - ./conf/hydra.env;
  5. Configure Docker Network
    - Set the “subject7“ network for “hydra“ docker container in the docker-compose.yml file.
      
      It should be configured as follows:
      
      services: hydra: ... networks: subject7_subject7-network: external: true
Summary
- Hydra upgrades automatically if already configured;
- Otherwise, install and configure it manually;
- Keep Vault credentials updated at every upgrade;
- Remove deprecated ActiveMQ settings;
- Ensure correct Docker network configuration.

Comments