Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Authentication to Secure LDAP causes Operations Error after upgrading to Business Mashups 2008 R2.02
SBM 2008 R2.02
CMS-XML Make JSessionID cookie hidden and secure
SBM 10.1.4
CMS-XML LDAP import using secure connection fails with error 81
SBM 11.0
CMS-XML AE Common Logger Oracle connection error with secure encrypeted Oracle connections
SBM 10.1.5.2
CMS-XML SSO and SSL: Only secure content is displayed and users get error about mixed content
SBM 10.1
CMS-XML Failed to construct cookie object when there is a space followed by the word Secure in the value of the cookie
SBM 10.1.4.1
CMS-XML Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
SBM 11.0
CMS-XML SAML2 - Since upgrade to 11.3.x it is not possible to connect via Composer - Error: Failed to retrieve valid security token from ... An unsecured or incorrectly secured fault was received from the other party
SBM 11.3.1
CMS-XML Add native capability in SBM Configurator to enable HSTS when HTTPS is enabled and HTTP is disabled
It allows web servers to declare that web browsers (or other complying user agents) should only interact with it using secure HTTPS connection and never via the insecure HTTP protocol.
CMS-XML SBM configurator eroniously report that Default certificates provided by Serena have been detected
Default certificates provided by Serena have been detected for the following components: SSO, Dimensions CM, Dimensions RM, PVCS VM. To secure your installation, you must generate new certificates. For more information, refer to the SBM Installation and Configuration Guide.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs