24.3 enhancements and patches


Review the BMC Helix SSO 24.3 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

Version

SaaS

On premises

Fixed issues

Updates and enhancements

24.3.01

✅️


None

24.3.00

✅️


For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.

BMC applies upgrades as described in the BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows.


24.3.01


Delete realms and authentication types

Administrators with restricted permissions can easily remove realms and authentication types in the chaining mode for dedicated tenants. 

Learn more about these actions in Adding-and-configuring-realms.


Change the default value of the SMTP timeout

To cater to an organization's needs, administrators can change the default value of the SMTP timeout session.

Learn about changing the default timeout value in Configuring-Local-authentication.

24301_SMTP timeout fields.png

What else changed in this release

Update

Product behavior in versions before 24.3.01

Product behavior in version 24.3.01

Ability for users to view their password on the  BMC Helix SSO login page.

The Show password option on the login page was unavailable to users.

The Show password option on the login page is available to users.

Multiple refresh tokens for a client ID and secret key pair.

A single refresh token was generated for a client ID and secret key pair.

Multiple refresh tokens are generated for a client ID and secret key pair.

24.3


Manually generate client secret keys

Administrators can manually create client secret keys for OAuth clients.

This functionality helps you define secret keys according to your organization policies, replace a lost or incompatible autogenerated key, and so on.

Learn more about this enhancement in Registering-OAuth-clients.

24.3_Additional secrets UI.png



Fetch specific user details via the OpenID Connect authentication method

While configuring the OpenID connect authentication, administrators can specify user details to be fetched from the userinfo endpoint to add another level of user authorization.

Learn more about this functionality in Configuring-OpenID-Connect-authentication.



What else has changed in this release

In this release, note the following significant changes in the product behavior:

Update

Product behavior in versions earlier than 24.3

Product behavior in version 24.3 and later

Change in the BMC Helix Single Sign-On server containers

The BMC Helix Single Sign-On server containers used Java 17.

The BMC Helix Single Sign-On server containers use Java 21.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*