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 DimCM: SSO: How to create standalone SSO certificates for Dimensions CM and establish a trust with the SSO Server
This document is for Dimensions CM 14.x and later versions and/or SBM 11.3.x. SBM 11.4 does contain a newer cm.pem file which may need to be applied to the Dimensions CM Server. If using older versions of Dimensions CM, please see Knowledgebase Solution S140601 .
CMS-XML SBM: Error "Failed to obtain security token" and "soap_wsse_verify_X509" when deploying to some environments
When SBM components are installed across multiple servers, each server must have matching signed certificate trust keys. This allows the servers to communicate with each other. If the certificates don't match, you could see any number of problems.
CMS-XML DimCM: When logging out of Web Client or AdminConsole, a Logout failed (USERNAME) occurs when using SBM SSO
This issue has only been seen when using SBM SSO Server, version 11.8, and an older version of Dimensions CM. This has been fixed in Dimensions CM 14.5.2. The SBM SSO Server allows for the logout request to be used with a CSRF token. Workaround: 1. On the SBM Server, locate the following file and make a backup copy:
CMS-XML Dim10: SBM2DM: After upgrading the Connector tool from TT2DM to SBM2DM, SBM issues are not created in Dimensions nor are SBM issues transitioned from Dimensions.
This issue occurs only if you have Status' mapped within the Connector as coming from TeamTrack and/or Dimensions. If they are mapped as 'both', no problems occur.
CMS-XML CM/SDA/SRA/SDA/RLM: Error "SSO Gatekeeper error has occurred: Error obtaining security token. Validation of WS-Federation token failed with code 40:Token issuer not allowed"
To update your SSO STS certificates: On the server where SBM is installed: If you are using SBM 10.1.1.4+:
CMS-XML How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
If the user exists in the client requesting authentication, the user will be logged in, otherwise a login failure will occur. For example, if I go to the Dimensions CM website, I will be redirected to the SBM SSO Engine where my login can be authenticated via LDAP. Finally, I will be returned to the calling product (application) with an authenticated token where my username will be mapped to the product's internal user database; if the username does not exist, login will not be granted .
CMS-XML SBM - Dimensions CM sync process crash, referencing C:\Windows\SYSTEM32\ucrtbase.dll
One cause of this problem is if the sync log files get very large, over 1Gb. Clearing out these large logs from the log folder should allow the sync process to start up normally.
CMS-XML Dim CM 2009 R2: UTF-8 files from SBM do not show umlauted characters correctly in Dimensions
Also note that /EXPAND does not do anything when the file has no variables in it (as is the case here.) However, it does cause the translation to occur on the server, which is what we want. Also, note that /EXPAND is ignored if the item type in question does not allow it in the process model - this is something to watch out for if it does not work.
CMS-XML Dim CM 12.2: alf_events_config.xml contents prevent SBM-CM orchestration from working
Most of the example data from the installed file has been stripped out and the project id has been replaced with a wildcard asterisk character. At this time we believe it's this change that allows the file to be processed correctly but investigations are continuing. With this file in place the following can be see in the SDP log file:
CMS-XML Dim2009R2: Web Service: CreateRequest call returning HTTP Status 500 and not returning data to SBM
net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source ) Caused by: java.lang.NullPointerException at com.serena.dmwebserviceimpl.DimensionsRequestOperations.createRequest(DimensionsRequestOperations.java:155) at com.serena.dmwebservices2.DmwebservicesSkeleton.createRequest(DmwebservicesSkeleton.java:519) at com.serena.dmwebservices2.DmwebservicesMessageReceiverInOut.invokeBusinessLogic(DmwebservicesMessageReceiverInOut.java:84) ... 24 more [ERROR] message cannot be null !!
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs