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 API fails to authenticate using NT Challenge Response authentication
API fails to authenticate using NT Challenge Response authentication
CMS-XML Events fail to send to OEGatewayService for anonymous events that do not include authentication causing orchestration to not run
Anonymous events received by the Event Manager that do not include authentication fail to send to the OEGatewayService so the orchestrations do not run. They appear to be received by the Event Manager and a match is found for the events, but the orchestrations do not run.
CMS-XML All communication from Tomcat to IIS fails if Client Certificate Authentication is enabled
IssueRequestHandler.processRequest(136): Error acquiring security token: Error authenticating user "aaaa": Web Services "https:// serverName :443/gsoap/gsoap_ssl.dll?sbminternalservices72" returned an error: "java.net.SocketException: Connection reset"
CMS-XML LDAP import using secure connection fails with error 81
SBM 11 fails with error message "LDAP bind authentication failure with Search Authority-Bind: 81 Server Down" The following three errors are logged in the application event log in this order: Error occurred in file:
CMS-XML Security token is sent even though Use SSO Authentication check box is not selected in Composer
If it is not selected, the security token is not added to HTTP header (this keeps the token from being sent when SSO is SBM-enabled, and is done so for security reasons). This prevents SBM from inadvertently passing the SSO token to non-SBM REST services. (Some services will actually fail if the SBM SSO token is present in the header when not expected).
CMS-XML SBM filling event logs with LDAP authentication messages
LDAP bind authentication failure with ou=people,o=test.com,o=SDS(uid=P4DTI-replicator0): 32
CMS-XML Unable to Delete when transition authentication is used on delete transition
"You have already started work on this item that has not yet been completed. If you wish to continue and discard your work on previous transitions, click ' Break Lock'. If you choose to break the lock, the record is not deleted and the loop persists to enter authentication and break lock until such time as cancel is chosen to break the lock.
CMS-XML How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
Once the user is authenticated via LDAP, a SAML token will be issued to the client for the user. 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.
CMS-XML Composer can not deploy when one environment is down
In certain circumstances an attempt to deploy to a working environment will fail , the message indicating the the " authentication server could not be contacted" on a different environment, that is currently unavailable. This can happen when the last deploy by this user of any ProcessApp was to an environment that is now unavailable, even when you are trying to deploy elsewhere. If you know the environment will be restored to activity soon, then Publish from Composer and Deploy from Application Repository.
CMS-XML Orchestration Engine Purge Utility: username/password with spaces.
When you run the purge utility in interactive mode, you may be prompted for a username/password. The authentication fails if there are spaces in either the username or password.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs