ESP Workload Automation Workstation Version 11.3 Build 116 released

[Jonas Dusil]

Dear ESP community,

We are happy to announce the release of version 11.3 Build 116 of ESP Workload Automation Workstation. 

 

Apart from fixing many issues, this enhancement introduces an optional Host Alias field to the Connection Manager dialog.
With this enhancement, you can increase the flexibility of securely connecting the ESP Workload Automation Workstation Client with the ESP

Workload Automation Workstation Server. The Host Alias field allows you to enter an alternative hostname should the

TLS certificate Common Name (CN) differ from the ESP Workload Automation Workstation Server address name.

Also the Workstation now uses OpenSSL 3.1 .

Please see the list of changes and download the build 116 at.
https://support.broadcom.com/web/ecx/solutiondetails?aparNo=LU13072&os=MS%20WINDOWS

Please refer to techdocs.broadcom.com for more details:

 Set Up a New Connection
 Add a Server Connection
 Modify a Server Connection

------------------------------
Jonáš Dusil
Product Owner | ESP Workload Automation | Mainframe Software Division
------------------------------

[Jonas Dusil]

Dear ESP community,

We have identified a problem in build 116 of ESP Workstation. In build 116, the user is unable to connect to ESP when using a one-time password together with the secure connection option. If you require the use of one-time passwords for users, we recommend that you do not install build 116. Our engineering team is already working diligently to resolve the issue, and we will update you when the new Workstation build is available.

We apologize for the problem. Please reach out to us with any questions.


------------------------------
Jonáš Dusil
Product Owner | ESP Workload Automation | Mainframe Software Division
------------------------------

[ERIC Foecking]

Jonas,

   Would you clarify what you mean by "one time password"?  Our use is for a new user with a newly established account.  They are given a temporary password that is forced to be changed on their first login.  If that is the same case, I would be curious how that might be different than any login where the password may have expired and is required to be changed.

Thanks,

 

[Jonas Dusil]

"One time password" in this case means any password that becomes inactive after the first security check. Your example is correct, and even a user that has the password set to expire during the first login will have a problem in build 116 when using the secure connection option. In our environment, we have already tested that the previously-mentioned scenario has been corrected for build 117 (currently being developed).

Regards,

------------------------------
Jonáš Dusil
Product Owner | ESP Workload Automation | Mainframe Software Division
------------------------------