25.4.01 enhancements

Review the deployment enhancements for BMC Helix Service Management on-premises 25.4.01 that will benefit your organization and understand changes that might impact your users.

Version	Fixed issues	Updates and enhancements
25.4.01	Known and corrected issues	25.4.01

Downloading and installing BMC Helix Service Management 25.4.01

Download from EPD	Downloading the installation files
Fresh installation	Installing
Upgrade	Upgrading

25.4.01

Use updated support for technology stack

BMC Helix Service Management supports the following technology stacks:

Kubernetes version 1.34
OpenShift version 4.19
Nginx Ingress Controller version 1.13.x and 1.14.0
Helm 3.19

For more information, see System requirements.

Enable realm identification by using patterns

Enable realm identification by using patterns to control user access based on the user name pattern and IP range pattern. This capability ensures that only approved users can log in to Service Management applications.

For more information, see Setting up the installation environment.

Remove obsolete container images

Remove obsolete BMC Helix Service Management container images in your Harbor registry to optimize storage and ensure security by retaining only approved images.

For more information, see Setting up a Harbor repository to synchronize container images.

Enable multiple domain authentication with BMC Helix Single Sign-On for seamless authentication

Enable seamless authentication between Service Management applications and the BMC Helix Platform hosted on different domains by using the ENABLE_RSSO_MULTI_DOMAIN parameter in the HELIX_ONPREM_DEPLOYMENT pipeline.

For more information, see Performing the BMC Helix Service Management installation.

Deploy infrastructure services required for CORE mode automatically

The BMC Helix Platform Common Services deployment manager configures the necessary infrastructure services required for BMC Helix Service Management CORE mode automatically when you set the SM_PLATFORM_CORE parameter in the deployment.config file. This automation efficiently streamlines setup and optimizes resource sizing based on deployment requirements.

For more information, see Installing BMC Helix Platform Common services 25.4.00.

What else changed in this release

The following table lists the changes in the product behavior in this release:

Update	Product behavior in versions earlier than 25.4.01	Product behavior in version 25.4.01
Change in the security certificate configuration process	To use a security certificate, you create the cacerts files in a specific format provided by BMC and then provide this file as the CACERTS_FILE parameter value in the HELIX_ONPREM_DEPLOYMENT pipeline.	You can directly provide a single certificate file or a ZIP file containing multiple certificates as the CUSTOM_CERTIFICATE parameter value in the HELIX_ONPREM_DEPLOYMENT pipeline. The CACERTS_FILE parameter in the HELIX_ONPREM_DEPLOYMENT pipeline is renamed to CUSTOM_CERTIFICATE. For more information, see Performing the BMC Helix Service Management installation.
Parameters added in the HELIX_ONPREM_DEPLOYMENT pipeline	The HELIX_ONPREM_DEPLOYMENT pipeline do not include the following parameters: ENABLE_RSSO_MULTI_DOMAIN HELIX_DSO	The HELIX_ONPREM_DEPLOYMENT pipeline includes the following parameters: ENABLE_RSSO_MULTI_DOMAIN—Use this parameter to enable BMC Helix Single Sign-On multiple domain configuration. HELIX_DSO—Use this parameter to enable the Distributed Server Option (DSO) service. For more information, see Performing the BMC Helix Service Management installation.