Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
HTML Solutions Business Manager 11.4.2 Security Bulletin
This document contains important security information for SBM . This document is only available to registered customers who log in to the Support site. Last updated on 2019-02-25.
CMS-XML SBM Security Bulletins
11.3.1 11.4.2 11.6
CMS-XML VM I-Net Web Client login fails with HTTP ERROR 403 for servlets using an SBM SSO server for authentication
This error can be the result of an SBM SSO security enhancement that was introduced in SBM 11.5.1, and then backported to SBM 11.4.2 . (For this reason the error can first occur if SBM was upgraded from either SBM SBM 11.5.0, SBM 11.4.1 or an older release.)
CMS-XML Database Clients and Drivers for SBM
SQL Server 2014 and higher with SBM 11.4.2 and higher – Use ODBC Driver 17 for SQL Server. For more information, see solution S143340.
CMS-XML How does the December 31, 2020 end-of-life for Adobe Flash effect SBM (Solutions Business Manager) and SSM (Service Support Manager) and RLC (Release Control)?
Once Flash is disabled, you will no longer be able to render Rich Graphical Reports, add/update users or permissions, make workflow or project level updates, add/update notifications, etc. SBM versions 2009 R1 through SBM 11.3.1 use Adobe Flash for Rich Graphical Reports and the web-based Application Administrator. Micro Focus removed Flash from these areas beginning with SBM 11.4, but we recommend upgrading to SBM 11.4.2 .
CMS-XML SBM: SECURITY BULLETIN - CVE-2021-44228 and CVE-2021-45046 - RCE 0-day exploit found in Log4J
that following versions of SBM ( 11.4.2 and 12.0) can be manually updated to log4j 2.17 using the following steps. Versions likely can be updated with some customer reports of success on 11.8 and 11.7.1, but have not been officially tested yet. If you find this does not work for your system, then return the original JAR files to their location and back out the changes.
CMS-XML SBM: How to upgrade SBM and move to a new Windows server at the same time
If you are upgrading from a much older version, you will need to upgrade in multiple steps. For example, if you are running 2009 R4, you will need to upgrade to SBM 10.1.5.4, then upgrade again to SBM 11.4.2 (or higher). In this situation, there are a few additional steps and considerations.
CMS-XML SBM user licenses, laptop and mobile/fixed devices
below. Also, note that if the user closes the browser in an SBM version older than 11.4, then the license release will not be triggered. Only the exit link in the UI will trigger the license release for versions prior to SBM 11.4[2 ]
CMS-XML Configuring SSO Protected Hosts
Starting in SBM 11.4.2 , you can use SBM Configurator to allow selected SBM component servers and other hosts in the continue and wreply HTTP parameters used with SSO redirects. This enables you to define hosts that have SSO protected applications. When enabled, SSO will refuse to accept requests or redirect to hosts that are not on the list.
CMS-XML 404 error when trying to load SSO login page - server.log has error regarding "sbmSAML2SPConfigFilter"
SSO login page is getting a 404 error when trying to load the IDP URL. This particular issue has been seen in SBM 11.4.2 , but it may exist in other versions as well. When looking at the Tomcat's server.log,
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs