22.2 enhancements and patches
BMC Helix Single Sign-On enhancements
Login name policies for BMC Helix SSO administrators and local users
The login name policies have been introduced for
BMC Helix SSO
administrators and local users. This improves the usability of
BMC Helix SSO
.For more information about the login name requirements for administrators, see Setting-up-BMC-Helix-SSO-administrator-accounts.
For more information about the login name requirements for local user accounts, see Managing-local-users-and-passwords.
What else changed in this release
In this release, note the following significant changes in the product behavior:
Update | Product behavior in versions earlier than 22.2 | Product behavior in version 22.2 and later |
|---|---|---|
Change password support for the authentication chain that contains preauthentication. | The change password functionality was not available for preauthentication. | The change password functionality is available for the authentication chain that contains preauthentication. For more information, see Password-change-mechanisms. |
Deprecation of the BMC Helix SSO installer. | The BMC Helix SSO installer was used for the application on-premises deployment. | The BMC Helix SSO installer is deprecated in favor of the application containerized deployment. For more information, see Deprecated-and-discontinued-features. |
Deprecation of the BMC Helix SSO Launchpad. | The BMC Helix SSO Launchpad was used as a start page for end users to access corporate applications. | The BMC Helix SSO Launchpad is deprecated in favor of BMC Helix Portal. For more information, see Deprecated-and-discontinued-features. |
Support for Java 11. | Java 8 was a minimum supported version. | Java 11 is a minimum supported version. |
Ability to set an environment parameter for the rsso-agent.properties file. | The default values specified in the rsso-agent.properties file caused permission issues for in-container configuration file modifications. | Any environment parameter can be inserted for the rsso-agent.properties file by using a special parameter format, which eliminates permission issues. For more information, see Configuring-the-BMC-Helix-SSO-agent. |
Option to configure token timeouts for multi-tenant clients. | A setting for the token timeout expiry period did not work for the BMC Helix SSO multi-tenant clients. | Token timeouts can be configured for the Native Client, Single-tenant Client, and Multi-tenant Client. For more information, see Configuring-OAuth-2-0. |