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 MCLG: How to setup Collage to run using SSL (https) instead of http?
These instructions show how to setup a "Self Signed" certificate and customize the Collage startup files to be able to use ssl and allow users to login via https. If you need instructions on how to install a certificate from a Certificate Authority such as Verisign, Thawte etc. see the following link for details. After installing the certificate the same customizations from a Collage standpoint illustrated in this document will pertain.
CMS-XML RESTGrid and RESTCaller and possibly other https calls originating in Tomcat does not work when the external proxy is configured.
if not "x%HTTP_PROXY_USER%" == "x" ( call :set_java_opts http .proxyUser "% HTTP _PROXY_USER%" call :set_java_opts http.proxyPassword "%HTTP_PROXY_PASSWORD%"
CMS-XML Address for external links requires http://, otherwise notification does not get sent
Ensure you use http :// or https :// is your link address when configuring this
CMS-XML This request has been blocked; the content must be served over HTTPS.
Given that SSL is enabled. If the user types: myserver.com/tmtrack/tmtrack.dll , the browser will assume HTTP with no S. The redirect to the SSO login page gets to the IDP using SSL, however, the following url is called using HTTP . Chrome does not allow the CSS to be downloaded so the user gets the default brown login page instead of the modern blue theme that is setup .
CMS-XML SAML2 setup fails with error "Unable to builder artifact for message to relying party"
To resolve, edit the IDP metadata located in the Configurator on third party authentication tab. Find these two lines and change the order so that HTTP-POST comes first. <md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings: HTTP -Artifact" Location=" https ://***/login"/>
CMS-XML Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
"This could be due to the fact that the server certificate is not configured properly with HTTP .SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server."
CMS-XML DIM10: Build fails when run from Build Console on WAS 7 via https
- Install Websphere Application Server 7 and all Dimensions 2009 R1.01 web applications - connect to the adminconsole via https (default is port 9443) ... The build should succeed as it does on Tomcat ( http or https ) and WAS 7 ( http only)
CMS-XML Problems using HTTPS / SSL with Java plug-in 1.6.0 Update 19 (or 1.5.0 Update 23) and later
... -Net over HTTPS (SSL) ... ... caused by a configuration change in the ... ... found here: http :// ... The behavior has been validated through JRE 1.6.0 Update 20, the current update as of this writing, and should also exist in JRE 1.5.0 Update 24 and later (per http ://www.oracle.com/technology/deploy/security/critical-patch-updates/javacpumar2010.html ).
CMS-XML Dim14: Installation: Upgrade: SSO: Gatekeeper-core-config.xml file has duplicate entries
... SecurityTokenService"> https :// ... ... SecurityTokenService"> https :// ... ... SecurityTokenServiceExternal"> https :// ... ... SecurityTokenServiceExternal"> https :// ... ... and consumed via HTTP 302 redirect (by default configuration ). <parameter Type="xsd:anyURI" name="FederationServerURL"> https ://DIMSERVER:8443/idp/login</parameter> <parameter Type="xsd:anyURI" name="FederationServerURL"> https ://DIMSERVER:8443/idp/login</parameter>
CMS-XML Event Response Code: 500 following the implementation of ChangeMan ZMF 8.2 Patch 3 - REST API (Revision-1)
After implementing ZMF V8.2.03 REST API Revision-1 and recycling the ZMF started task and Tomcat server, the existing subscriber got an HTTP 500 Response Code: ... They had the AT-TLS rule encrypting all ports AND they had configured Tomcat to secure ports ( HTTPS ), so it appears that their issue was caused by double encryption. ... The customer’s requirement is just that the connection is secured ( HTTPS ), so they can do that via AT-TLS rules or native security within the application (Tomcat).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs