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 "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 Dim14: SSO: Default Certificate for FEDSRV due to expire
When using the Dimensions SSO Server with CAC or SmartCard enabled for login, one of the default certificates is due to expire on 13 June 2015. This will only affect the Web Client users who use the SmartCard Login button if not corrected.
CMS-XML Dim14.2: SSO: SOAP message MUST NOT contain a Document Type Declaration(DTD).
After installing the Dimensions SSO Server for use with Dimensions CM, the following error occurs when accessing the Web Client and/or Admin Console.
CMS-XML Dim14.2: SSO: PRG7700105E Error: Failed to connect to the Serena Single Sign On server
After configuring Dimensions to use an SSO Server which has SSL enabled, the following error can occur when attempting to access a non-Java client, such as DMCLI, Desktop Client, etc: PRG7700105E Error: Failed to connect to the Serena Single Sign On server, please check the server is running and is correctly configured.
CMS-XML Dim2009R2: SSO CAC: Error authenticating user: Cannot initialize LDAP context or Invalid username or password
The above error occurs if Dimensions application is not connecting to the LDAP Server correctly through SSO . To check connections, perform the following: 1. Disable SSO and CAC as follows: a. Make a backup copy of the following files which will make reverting back to SSO/CAC a bit easier.
CMS-XML Dim2009R2: SSO CAC: Certificate principal not found in LDAP
Dim 2009R2: SSO CAC: Certificate principal not found in LDAP
CMS-XML Dim2009R2: SSO CAC: OMException in getSOAPBuilder
The below error can occur when attempting to login into the Web Client with SSO CAC enabled:
CMS-XML DimCM: Git Connector SSO CAC: Activ Client library cannot be used due to a missing or invalid path variable. Please add acpkcs211.dll path to the git-dm configuration.
DimCM: Git Connector SSO CAC: Activ Client library cannot be used due to a missing or invalid path variable. Please add acpkcs211.dll path to the git-dm configuration.
CMS-XML Dim: SSO: Enabling SSO to work with silent connections PDIFF: PRG7700110E Error: Untrusted endorsing credentials
Configuring CM to use SSO out of the box with SBM as the authentication.
CMS-XML Dim2009R2: SSO CAC: Invalid User Name or Password or ACL7700119E Cannot confirm certificate authenticity
When using the Web Client with SSO CAC enabled, the following error is occurring for some users on login: Invalid User Name or Password
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs