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 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 KM-DIM2009R2: How to configure Tomcat to use SSL with a self-signed certificate
port="8443" scheme="https" secure ="true" sslProtocol="TLS" strategy="ms" truststoreFile="C:\Temp\.keystore" truststorePass="serena"/>
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 How to configure one-way and two-way SSL for Release Control and ZMF Connector
4. Edit the SBM links in the zmfalf_resource.properties file (..\common\ tomcat \8.0\webapps\almzmfalf\WEB-INF\conf) to receive ALF Events on the secure SBM port, such as https://<sbmhostname>:8443.
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 Installing a Secure Version of the ChangeMan ZMF REST API-Jenkins Integration
ZMF REST Services Getting Started Guide, all secure communication functionality (i.e. SSL) associated with this processing on z/OS must be implemented using IBM's Application Transparent Transport Layer Security (AT-TLS). Some customers may have found and implemented other solutions that address their specific needs (e.g. the implementation of native Apache Tomcat SSL connectors). However, if problems are encountered
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.
MS-WORD SSL Certificate with own CA Certificate.docx
<Connector SSLEnabled="true" acceptCount="100" clientAuth="false" disableUploadTimeout="true" enableLookups="false" keyAlias=" tomcat " keystoreFile="conf/sample- ssl .jks" keystorePass="serena" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8443" scheme="https" secure = "true" sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs