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: SSO Login fails with error "Failed to verify signature"
Examining the file sso - idp.log
CMS-XML VM shows SSO Login Error: Connection exception using TOKENSERVERURL "http://ServerName:8085/TokenService/services/Trust": Transport error: 404 Error:
VM 8.5.2 introduced logic that allows VM to continue using TOKENSERVERURL and SSLCLIENTAUTHURL directives in configuration files (CFG) that contain the old-style /TokenService/services/Trust URL to refer to the SSO STS server, rewriting those URLs on the fly to the new /idp/services/Trust
CMS-XML VM Configure Project Login source needs to be able to use and create SSO URIs containing "idp"
As of SBM 10.1.3, the preferred way to communicate with an SSO server running on SBM is via the webapp "idp". Unfortunately Version Manager's Login source screen in Configure Project does not allow for this, as it does not expose the URI itself but constructs one behind the scenes based on information provided to the UI. This means VM continues to use the webapps "TokenService" and "ALFSSOLogin".
CMS-XML VM: How to import an updated SSO STS Trust Certificate / How to solve "Invalid SSO token" errors
SSO/CAC Error : Invalid SSO token, validaton result: 40 Error signing on to File Server: "Token issuer not allowed ". VM I-Net web client:
CMS-XML Version Manager SSO Login Error: Connection exception using TOKENSERVERURL "...": Received fatal alert: bad_certificate.
After you export this certificate you will need to copy it to a location you have access to for the machine having the problem. This can either be copied locally on the machine or a network location you have permissions to.
CMS-XML Version Manager desktop client has grayed out Smart Card Login button on the SSO Login dialog (CAC login)
library = C:/Program Files/ActivIdentity/ActivClient/acpkcs211.dll As of VM 8.6, the library path is allowed to have quotes.
CMS-XML Utility to update the SSO (Serena Single Sign-On) certificates used by PVCS Version Manager
/TokenService/services/Trust": Authentication failed Error: Token issuer not allowed Error signing on to File Server: "Token issuer not allowed".
CMS-XML Version Manager SSO: Default Certificates for STS, GATEKEEPER and VMSERVER expire starting June 13th 2015
/TokenService/services/Trust": Authentication failed Error: Token issuer not allowed Could not authenticate (Unable to connect via the server-side processing.
CMS-XML Fix for defect DEF188927 - VM SSO problems with SourceBridge
Fix for defect DEF188927 - VM SSO problems with SourceBridge
CMS-XML SSO: LDAP: Use the Compound Authenticator to authenticate against one or more authenticators
SSO : LDAP: Use the Compound Authenticator to authenticate against one or more authenticators
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs