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 VM HOST login source can fail when using 3rd party NSS libraries to provide user/group ID access
The Version Manager installer was not able to run the command lsb_release , for example because the administrator did not install the package redhat-lsb-core The reason for this is that the 3rd party NSS libraries may be incompatible with the library libfreebl3.so
CMS-XML Version Manager HOST login source does not work on Linux when the OS is configured to use winbind or SSSD
If y If your Linux system is configured to use winbind for user authentication, querying your Windows Active Directory Server for user credentials and group membership, or if it is configured to use the System Security Services Daemon (SSSD), the Version Manager HOST login source may fail to return a username. When this happens, users may get errors like:
CMS-XML Eclipse RIDE and Visual Studio RIDE clients can no longer login via Server-Side processing after the 8.5.2 or 8.5.3 patch was installed on a VM 8.5.0 server.
If a Serena VM Web Application Server that used to run VM 8.5.0 has been upgraded to VM 8.5.2 or 8.5.3 by applying the corresponding patches, Eclipse RIDE or Visual Studio RIDE clients may fail to login the user if Server-Side Processing has been enabled, showing an Unable to authenticate user Username error instead. If this happens, check the file VM_Install_Dir
CMS-XML VM 8.6.1+: Web Client shows SSLHandShakeException PKIX path building failed when trying to login to SBM to use Associate Issue
Log in to the machine running the VM Web Application Server as the user who installed Version Manager. On Windows open a Command Prompt on the server in Administrative mode (right-click | Run as administrator) Run the command:
CMS-XML VM: SSO Login fails with error "Failed to verify signature"
An attempt to login to Version Manager that is configured to use an SSO server fails . The login page shows the error Failed to verify signature
CMS-XML Version Manager cannot login to an SSO-enabled Project Database using a CAC reader when ActivClient 7 is installed
When ActivIdentity's ActivClient 7 is installed on a computer, Version Manager fails to login to an SSO-enabled project database using a CAC (Common Access Card) reader. Depending on the exact version of ActivClient that is used, one of the following errors is shown:
CMS-XML VM 8.0.0.3 to Mover 1.0 migration. Moving to new server. Login failed errors.
Unable to get Mover 1.0 to authenticate user logins to VM 8.0.0.3 (this is for the VM/DIM authentication install of Mover). The admin account works fine, but none of the other user accounts works.
CMS-XML VM 8.5.0 - 8.5.2: SSO login does not work when using SmartCard Login button (CAC login) from the VM I-Net web client
When a user of VM I-Net presses the SmartCard Login button (CAC login ) to login to a Version Manager Project Database that is configured to use a Version Manager SSO server, that login attempt fails with the error: Untrusted endorsing credentials.
CMS-XML VM 8.6.1 DEF322905: HotFix for VM 8.6.1 Web Client to fix Login Time-out and remove dependency on reg.exe
DEF322905: VM 8.6.1: VM I-Net Web Client Agent install fails on Windows when users do not have access to reg.exe
CMS-XML Configuring multiple LDAP servers for redundancy has an unexpected side-effect in VM 8.2 - VM 8.4.4
Unfortunately this results in an unexpected side-effect if the servers are mirrors of each other, and are only specified for redundancy purposes. When a user enters an incorrect password, Version Manager will incorrectly attempt to log the user into each of the LDAP servers that is configured. If all LDAP servers tap into the same database, and there are more LDAP server configured than the maximum number of failed login attempts that are allowed for the domain, the user will lockout their account with just a single failed login attempt into Version Manager.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs