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 Version Manager Rich IDE (RIDE) integrations fail to connect to SBM with error "Could not authenticate (Invalid user)"
Example: Restart IIS, for example by executing "iisreset" from an Command Prompt window The second variant of the error, where someone was able to get a working RIDE workspace with SBM integration, would normally indicate that the option was selected at the time the RIDE workspace was setup, but that it has since inadvertently been disabled.
CMS-XML VM 8.5.2: Patch for Version Manager 8.5
... network protocol ( Windows , Linux, ... Support for Windows Server 2012 R ... on Windows , Linux or ... ... network protocol ( Windows , Linux, ... Support for Windows Server 2012 R ... on Windows , Linux or ... 1.1.6 New axis2 temp file handler breaks multiple PCLI processes running in parallel on a single system if SSO login is used [DEF261700] ... PCLI processes that authenticate via SSO. ... network protocol ( Windows , Linux, ... Support for Windows Server 2012 R ... on Windows , Linux or ... ... network protocol ( Windows , Linux, ... Support for Windows Server 2012 R ... on Windows , Linux or ... 1.1.6 New axis2 temp file handler breaks multiple PCLI processes running in parallel on a single system if SSO login is used [DEF261700] ... PCLI processes that authenticate via SSO. 2.1.1 VM patch cannot be installed on systems lacking the Desktop Client feature [DEF226981] ... VM release on Windows , it will ...
CMS-XML VM 8.6.1: In-place upgrade from VM 8.6.0 fails with Restore report showing a failure for the file gatekeeper-core-config.xml
The following steps assume that Version Manager is not configured to authenticate users via a Serena SSO server (from VM or SBM ) as it deploys the default file from the new VM release. ... 20190415-164431: Current OS : WINDOWS
CMS-XML Version Manager SSO Login Error: Connection exception using TOKENSERVERURL "...": Received fatal alert: bad_certificate.
... as part of SBM 11 or newer ... SSL Client Certificate Authentication ... , attempts to authenticate with a Username ... Serena PVCS Version Manager (PCLI) v8.5.3.0 (Build 071) for Windows NT/80x86 ... SSO Login Error: Connection exception using TOKENSERVERURL "https:// sbm -server-name:8443/TokenService/services/Trust": Received fatal alert: bad_certificate. This is caused by version manager not being able to supply a required certificate needed by SBM for client authentication .
CMS-XML What Version Manager releases support SSO authentication using an SSO server running on SBM 11.1?
Starting with SBM 11.1, the TokenService and ALFSSOLogin redirectors that were used to support pre-idp SSO authentication are no longer supported, leaving just the new-style authentication via idp
CMS-XML One or more VM I-Net Web Client users find that module assocations made via SourceBridge do not get stored if VM and SBM are both using SSO authentication
In a setup where SBM and VM are both configured to use SSO authentication , some users may find that SBM issues they associate during checkin do not get stored, despite those users being able to select and assocate issues in the SourceBridge Web Client dialog.
CMS-XML VM I-Net Web Client login fails with HTTP ERROR 403 for servlets using an SBM SSO server for authentication
Access to DNS_Name_of_ SBM _SSO_Server was denied You don't have authorization to view this page.
CMS-XML Issues window is blank when using RIDE, VM 8.3 or 8.4 and SBM 2009 R2 or R3
Issues window and listing reports in SBM are blank when RIDE is used to link Version Manager 8.3 or 8.4, Visual Studio 2008 and SBM 2009 R1, R2 or R3. It has been determined that this problem only occurs if the IDE folder contains anything other than links to issues/items, like reports or other links. Another possible symptom is that while the window is not blank, the description field for anything other than an issue is blank.
CMS-XML Enabling IIS 7 for Version Manager I-Net breaks access to SBM on the same server
If VM I-Net is installed on a Windows server using IIS 7, enabling access through IIS will break access to SBM (and any other product using .dll in the URL). Attempting to go to http://server/tmtrack/tmtrack.dll? will show an error originating from Version Manager's Tomcat application server.
CMS-XML VM with SBM 11.7+ SSO: DaemonServer crashes using VM I-Net Web Client or RIDE with server-side processing
When a project database uses an SBM 11.7+ based SSO server for user authentication , attempts to get or update a file from a Web Client, or from a RIDE integration using server-side processing, will cause the client to hang or fail because the DaemonServer process on the server crashes. Affected operations include: Add Files
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs