This section provides instructions on how to enable SSL for IIS connections in Business Mashups. The following instructions apply to both self-signed and certificate authority–signed certificates. The party that ultimately signs the certificate request is not discussed below.
The section in the Administration guide on how to setup Tomcat to use SSL simply points to the online Tomcat documentation. Here is a quick guide on how to generate a self-signed certificate and how to setup Tomcat to use it.
There may be a situation where the ssl certificate being used to make a secure LDAP connection appears to be valid by all accounts yet the test connect still won't work. You may see an error like the following in the Event Viewer as a result.
If you are using LDAP with SSL , you might get authentication failure message when doing Test Connection from the SBM Configurator. "LDAP bind authentication failure with Search Authority-Bind: 81 Can't contact LDAP server" Please check the event viewer for the detailed message on this error.
There are several ways to implement SSL in Business Mashups. The Installation Guide describes the basic steps that are necessary to establish SSL for IIS and JBoss, as well as additional steps you can follow if your server certificate is not signed by a well-known authority. The example provided in the guide for creating a self-signed certificate shows how to create a CA and certificate using openSSL.
We did not find any matches for your request Unknown error received from https....... The attached video goes through the steps to make sure JBoss / Tomcat has the appropriate ssl certificate so a trusted connection can be made and the results displayed.
Before you begin, you must get a certificate from a well-known certificate authority (CA) or generate one from your own CA. This certificate must be a PFX file.
