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 LDAP and SSO: When the SearchBase of an LDAP look up of Active Directory Server is set to the root of the tree, it is possible to get PartialResultException - Error processing LDAP search result(s): null
When the SearchBase of an LDAP look up of Active Directory Server is set to the root of the tree for LDAP and SSO then authentication does not work. If you have "referrals" selected then you get the following error in sso - idp.log : Example error:
CMS-XML Null Pointer Exception Error in RemoteUserFilter when turning on TRACE log level
we get an NPE and server is unusable. The SSO - IDP.LOG file may show something like this.
CMS-XML All communication from Tomcat to IIS fails if Client Certificate Authentication is enabled
In the sso - idp.log file, a connection reset error appears:
CMS-XML non-ASCII "allow search" fields do not work correctly - SSO errors
For a searchable field, enter a non-ASCII string, such as "Системная". If you have SSO enabled, this will change the search field to "searching" and the query never returns.
CMS-XML Cannot select NTLM with SSO in 10.1.3.x in Configurator
To workaround this problem we have modified the documentation to set the authentication type in this setup to LDAP while still maintaining the waffle and NTLM filters enabled. This would allow to user to access AE and AR via NTLM setup get logged on automatically once they have been verified against the domain and when connecting through composer it would validate the user against LDAP.
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 "Request is expired." received when attempting to login via SSO
"Request is expired." received when attempting to login via SSO
CMS-XML SRC: sso timeout not handled by announcement polling
SRC: sso timeout not handled by announcement polling
CMS-XML An exception occurs in solfwk log after SSO token expiration (Intermittent)
An exception occurs in solfwk log after SSO token expiration (Intermittent)
CMS-XML When SSO Login Form sits too long user is prompted to login twice
When SSO Login Form sits too long user is prompted to login twice
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs