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
CMS-XML How to test whether JBoss or Tomcat is able to communicate with a https (secure) website.
When the SBM JBoss/Tomcat server needs to use a secure url using SSL (HTTPS), it is crucial that the Java Runtime Engine (JRE) used by SBM can verify the SSL certificate. This is not a problem when the certificate is a public one, obtained from the commercial Certificate Authorities (CA) Java knows about, but it can become problematic when the SSL certificate is either self-signed or signed by a non-public Certificate Authority.
CMS-XML Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
If you try to connect Composer to the repository using a secure connection, you may get the following errors when it tries to connect. This would by default try to use the 8243 JBoss/ Tomcat port.
CMS-XML Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/TLS secure channel with authority
If you are not using SSL then in Configurator deselecct the SSL configuration for Tomcat . Untick "Use HTTPS on Port" and Apply.
CMS-XML How to configure the Cipher Strength for SBM Tomcat
SBM has an IIS/Windows component and a Tomcat component that can be secured with SSL . IIS/Windows is often setup by group policy to disable the use of weak SSL ciphers. However, the Tomcat component is not affected by group policy. Furthermore, the default setup of Tomcat is to allow the use of weak SSL ciphers.
CMS-XML How to setup jboss web server to use the same SSL key pair as IIS -- 2009R3 and later
When SBM is configured with the Application Engine and JBOSS servers on the same server, it is possible to setup the JBOSS Tomcat web server to use the same SSL key pair used to secure IIS. This article assumes that IIS has already been configured to use SSL. This how to is for SBM 10.1 and higher.
CMS-XML OE database fails to upgrade: Tomcat server startup timed out
Tomcat server startup timed out. ---> ConfigurationUtility.Core.Network.HttpException: URL: https://sbmp02/, Method: GET, Error message: The request was aborted: Could not create SSL /TLS secure channel.
CMS-XML Tips for Securing SBM Server
Use SSL: Make sure to use well-known SSL certificates in IIS and Tomcat (if you have HTTP ports active). Vulnerable TLS:
CMS-XML How to configure the Cipher Strength for SBM JBOSS
SBM has an IIS/Windows component and a JBOSS/ Tomcat component that can be secured with SSL . IIS/Windows is often setup by group policy to disable the use of weak SSL ciphers. However, the JBOSS/Tomcat component is not affected by group policy. Furthermore, the default setup of Tomcat is to all the use of weak SSL ciphers.
CMS-XML Suggestions for placing SBM server in the cloud
The repository would be accessed via the Tomcat ports. Have users accessing the repository connect to a VPN which will have access to the Tomcat SSL port 8243. "Most secure " here does not imply that internet access to the repository is not secure , only that internet access to the repository gives an authenticated user access to modify a process app. If internet access is desired for the Application Repository then consider using the option to "Use IIS to proxy all connections" which is located in the Component Servers section of the SBM Configurator.
CMS-XML How to acquire the SSL certificates for your mail server when setting up the Mail Client ( EOF on Socket ) error in ns.log
The attached video shows how to get a copy of the SSL certificates being used by your mail server in order for them to be imported into the JBoss/ Tomcat keystore.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs