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 "PRG7700105E Error: Error authenticating user (-1,073,741,715): Logon Failure" when using SSO to connect to Dimensions Desktop Client
DMPOOL 2015/01/16 12:34:53 E P60308 T59876 Authentication failed for user xxxxxxxx - 3 () When looking at the SBM SSO logs (by default, located at C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\ sso - idp.log ), you will see these errors: IssueRequestProcessor.process(426): Error invoking WS-Trust request: Authentication failed
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 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"
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"
CMS-XML SDA Plugin: SSO "false" option gives "-- ERROR: No information found! --"
Customer wants to ensure that every deploy goes through the correct RLC process. To make sure this happens, they do not want to give SDA deploy permissions to individual users. They want to setup one SDA service account, and only this service account would have deploy permissions. However, when they change the SDA plugin to be SSO "false" and they try to create a task, the system gives error "-- ERROR: No information found!
CMS-XML Cannot increase SSO session lifetime beyond 8 hours from SBM Configurator
</setting> in the SSO IDP server's Configuration.xml file, which controls the maximum time a token can live, but the default session token lifetime defined in the gatekeeper files remains unchanged. As the effective token lifetime is the lesser of the maximum time permitted by the IDP server (which is changed) and the default lifetime requested by the gatekeeper (which is not changed), you cannot increase the SSO session lifetime from SBM configurator beyond the 8 hours default (= 28800 seconds) that SBM ships with.
CMS-XML ZMF Connector gives error "Invalid element" or "Content is not allowed in prolog" or "Unexpected subelement hostAddress"
04-04@20:27:17 [http-8080-2] ERROR [SoapSSOUtils.java:269] [] : Exception happened while parsing the SSO token org.xml.sax.SAXParseException: Content is not allowed in prolog.
CMS-XML SBM 10.1.5.1 external tmtrack virtual directory not allowing authentication
This problem is fixed in SBM 10.1.5.2 for non- SSO use cases. If you are using SSO to manage user sessions with an external virtual directory in 10.1.5.2, you will perform steps 6 and 7 below.
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
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs