Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Composer fails to connect to the repository using HTTPS after successfully connecting using HTTP
Connection to the repository might fail with: Failed to retrieve valid security token from https://ApplicationRepositoryServer:8243/idp/services/trust for user (username)
CMS-XML Repository does not fully load and does not display all content.
When SBM is behind a firewall, it can be used with mixed content where it uses both HTTPS and HTTP. Under this circumstance, the Repository may not fully load and does not display all content.
CMS-XML HTTPS error when connecting in Composer or Connection attempt failed.
Connection attempt failed. Could not connect to the Repository .
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
Composer is trying to connect via https even though the Use Secure Connection is NOT ticked. Get the following error.
CMS-XML How does SBM Composer connect to the Application Repository?
"Failed to retrieve valid security token from [STS URL]" -- Review the URL and ensure that it is correct. Is it using HTTPS ? If so, is the port correct?
CMS-XML Logging into Repository or Composer gives "Authentication Failed: Unable to contact Authentication Service"
Please try the following: Type https :// at the beginning of the address you are attempting to reach and press ENTER. HTTP Error 403.4 - Forbidden: SSL is required to view this resource.
CMS-XML Logging into Repository gives error "Authentication error: A Soap fault occurred while contacting the authentication service"
AuthenticateServlet -- Exception caught: Failed to obtain security token: Error authenticating user "xxxx": Web Services " https ://ServerName:443/gsoap/gsoap_ssl.dll?sbminternalservices72" returned an error: " ITServices.corp.local" [http-]
CMS-XML Cannot connect Composer to Application Repository
Microsoft provides the following KB advising how to disable SMBv1: https :// The above error messages come about when SMBv1 is disabled via registry settings (SBM1 set to 0) as described in the article above.
CMS-XML HTTPS hostname wrong: should be ...
The solution to this problem is to add to the JBoss Hosts file (C:\Windows\System32\drivers\etc\hosts), a line with the NAT IP address of the Endpoint and its actual hostname ( i.e. not the local one). Then add to the Endpoint field in the Application Repository , the actual name Endpoint hostname which will be resolved via the Hosts file.
CMS-XML How to setup SBM to run using SSL (switching from http to https - SBM 10.x)
Part 3: Update the SBM Application Repository configuration These steps are particularly important if users are limited to access the system ONLY using SSL. Log into the SBM Application Repository (by default located at https://serverName:8243/mashupmgr ).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Comparing files (demonstration)
This Dimensions CM demonstration shows you how to compare two item revisions in the repository, and compare an item revision in the repository with a file in a work area
Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs