• SBM-API Authentication The SBM API provides Web services via the Simple Object Access Protocol (SOAP) protocol, which enables integrations with external systems. The protocol can be configured to run over SSL using customer credentials for authentication. Additionally, all interaction is controlled by the role of the authenticated user, which provides additional security such that unsolicited users cannot access restricted data in SBM.
▪ General logging for both the Notification Server and Mail Client and the connection timeout setting. ▪ Options for sending a notification to the administrator when an error occurs. ▪ The option to configure SSL for the Notification Server and Mail Client has moved from SBM System Administrator and is now handled by importing certificates into the JBoss truststore.
... SQL Server using SSL . ... negotiate to use SSL therefore you do ... ... relevant to the SBM Application Engine and Configuration Settings ( This ... your version of SBM and whether you ... ... your SQL Server SSL certificate into the Windows Certificate Store. Open the SBM Configurator and add either "; ssl =require ... or "; ssl =request As of SBM 10.1 ... ... the "; ssl =required" ... your SQL Server SSL certificate chain into the ... ... located in [ SBM Install Directory] ... use "; ssl =authenticate [ SBM Install Directory] ...
... SQL Server using SSL . ... negotiate to use SSL therefore you do ... ... relevant to the SBM Application Engine and Configuration Settings ( This ... your version of SBM and whether you ... ... your SQL Server SSL certificate into the Windows Certificate Store. Open the SBM Configurator. In SBM 11.3 ... select "Use SSL " on the ... In SBM 11.0 ... either "; ssl =required" ... or "; ssl =requested" As of SBM 10.1 ... ... the "; ssl =required" ... your SQL Server SSL certificate chain into the ...
... that the server certificate is not configured properly with HTTP ... If you look at the following file in your SBM installation (depending on the version of SBM you may use JBoss or Tomcat) ... C:\Program Files\Serena\ SBM \Common\jboss405\server\default\deploy\jbossweb-tomcat55.sar\server.xml ... C:\Program Files\Serena\ SBM \Common\Tomcat 7.0\server\default\ conf \server.xml
Once a self signed certificate is added to the Security - SSL Integrations section in configurator you can not over write it again later using Configurator.
The OpsHub SCCM Connector 4.5 couldn't connect from SBM to SCCMS through the OpsHub SCCM Connector. There is a bug in the SCCM connector and fixed it by adding the SSL certificates into "Trusted People\Local Computer"
The SSL certificate that SBM is using is either missing or out of date. You can verify with certificate is being used by checking the System Administrator under Options | Settings, on the SSL tab.
The fix for this problem will be to disable SSL configuration if using temporary profiles. Example of the start of the message is as follows: See the end of this message for details on invoking
