What’s new in 6.3.1.0
This topic provides the new features and enhancements that are introduced in this release.
New Features
- Log in to Sterling Control Center using single sign on (SSO):
Support has been added for single sign-on (SSO) using the SAML protocol through Sterling Secure Proxy and the Sterling External Authentication Server. For more information, see IBM Sterling Control Center SSO Configuration.
Note:The following are the prerequisites:- SSP version 6.1.0.0 iFix01 or later
- SEAS version 6.1.0.0 iFix01 or later
- TLS 1.3 enabled for internal and external connections in Sterling Control
Center:
TLS 1.3, a crucial internet security protocol, introduces enhancements in security, performance, and privacy. For more information, see Securing the IBM Sterling Control Center Monitor using Transport Layer Security 1.3 .
- Failed login attempts recorded in audit logs:
Enhanced logging now captures details of failed login attempts. When users access the Sterling Control Center console, both successful and unsuccessful login attempts are documented in the audit logs. This feature empowers administrators to track system access, providing insights into user activity and identifying failed login attempts resulting from improper access. For more information, see Displaying the Audit Log.
- Support for picture IDs enhances logged in user
identification:
Users now have the capability to upload picture IDs to their user profiles in Sterling Control Center, allowing for a personalized user experience. For more information, see Setting the Profile Picture for the IBM Sterling Control Center Monitor Web Console.
- Removal of escalated permissions for running containers:
The need for root access when running containers has been eliminated.
- Control Center FTP Agent:
The FTP Agent uses OSA approach to monitor FTP logs and post events to Control Center Monitor.
- Custom deployment scripts for Sterling
Connect:Direct.:
Administrators have the capability to upload and execute custom pre and/or post-deployment scripts in the context of Sterling Connect:Direct installations. These scripts can be triggered either before and/or after the installation or upgrade process. Examples of actions that custom scripts might perform include conducting pre-install or upgrade environment checks or executing post-install or upgrade tasks, such as uploading a connectivity check script. This flexibility allows administrators to tailor the deployment process to specific needs and requirements. Fore more information, see Custom Scripts.
- Support for certificate authority (CA) certificates for Sterling
Connect:Direct during initial deployments using Control Center
Director:
when creating new deployment package user can specify a CA and server certificate. Fore more information, see External Certificates.
- Efficiently compare entire Netmap from one Connect:Direct server with
another to troubleshoot communication between servers.:
This is also useful when deploying a new Connect:Direct server into a large environment. For more information, see Configuration.
Stack Updates
- Control Center is bundled with Java 17 JRE
- Support for Microsoft SQL Server 2022 for Control Center database
- Jetty 11
- Red Hat OpenShift Container Platform:
- 4.11.0 or later fixes
- 4.12.0 or later fixes
- 4.13.0 or later fixes
- Kubernetes >= 1.24 and <= 1.27
- Helm >= 3.10 and <= 3.13.x
- RedHat - UBI 9.2.x