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 DimCM: When logging out of Web Client or AdminConsole, a Logout failed (USERNAME) occurs when using SBM SSO
The SBM sso -idp.log file shows the following:
CMS-XML SSO Login does not present an error when SBM authentication fails
SSO Login does not present an error when SBM authentication fails - the user just gets the successful logout screen
CMS-XML VM and SBM SSO error on logout
When PVCS Version Manager is configured to use SBM SSO, a "logout failed" error message appears in the UI. To reproduce: 1) Login to the PVCS Version Manager Project Database in the VM Web Client. 2) Logout fails from the VM PDB
CMS-XML Dim Cm 14.3.2 / Remote deploy in a 12.x agent machine executing post-script fails with "COR1601051E Agent system doesn't have the capability to handle certificates for users using single-sign-on: certificate generation is not possible"
COR4501136E Error: Failed to execute post-script "post_qa.tpl" (Job R-57025349) for Area "AREA_QA" ( exit code: 0)
PDF RLM_IG.book
... interface, configuring 49 users, managing 43 views, configuring 52 Serena Release Vault configuring to provide baselines 32 configuring to provide requests 32 connecting to SBM 31 event notifications 35 installation 17 post-installation 28 requests, filtering 33 shell UI, exiting 40 snapshots promoting 24 software compatibility 10 solution importing 23 solutions for failure conditions 59 SSO existing Dimensions CM installations 17 new Dimensions CM installations 17 stages configuring 54 states configuring 53 status history 58 streams Dimensions CM 41 Serena Release Vault 41 system requirements 11
PDF Serena Release Manager Installation and Configuration Guide
... configuring 58 Serena Release Vault configuring to provide baselines 32 configuring to provide requests 32 connecting to SBM 31 deployment units, filtering 40 installation 17 post-installation 29 requests, filtering 40 server requirements 12 shell UI, exiting 46 snapshots promoting 25 software compatibility 10 solution, Serena Release Control importing 23 solutions for failure conditions 85 specifying DCR and DU providers 39 SSO existing Dimensions CM installations 17 new Dimensions CM installations 17 stages configuring 63 status history 84 streams Dimensions CM 48 Serena Release Vault 48 system requirements 11
PDF Serena Release Manager Installation and Configuration Guide
... Tomcat 20 post-installation 33 requests, filtering 45 users 58 servers Nolio, accessing 61 recommended 16 recommended configuration 108 requirements 13 shared by Serena products 20 shared time optimizing 108 shell UI, exiting 50 snapshots promoting 29 software compatibility 12 solution, Serena Release Control importing 27 solutions for failure conditions 105 specifying DCR and DU providers 44 SQL Server database, for Nolio 43 SSO existing Dimensions CM installations 20 new Dimensions CM installations 20 stages configuring 79 status history 104 streams Dimensions CM 59 Serena Release Vault 59 system requirements 13
PDF Serena Release Manager Installation and Configuration Guide
Index T recommended configuration 141 relating to environments 59 requirements 15 Serena Release Automation, accessing 72 time, optimizing 141 shell customizing 128 installing 39 upgrading 94 shell UI, exiting 58 snapshots promoting, in SBM 36 software compatibility 15 solution, importing 34 solutions for failure conditions 137 specifying BCR providers 78 DCR providers 79 DU providers 83 RFC providers 77 SSM configuring RFC reports for 131 sending information to 131 SSO existing Dimensions CM installations 26 new Dimensions CM installations 26 stages configuring 106 status history 136 streams Dimensions CM 70 system requirements 15
PDF Serena Release Manager Installation and Configuration Guide
... 163 relating to environments 50 requirements 17 Serena Release Automation, accessing 86 time, optimizing 163 shell installing 36 UI, exiting 49 upgrading 117 snapshots promoting, in SBM 40 software compatibility 17 solution, importing 37 solutions for failure conditions 155 specifying BCR providers 99 DCR providers 100 DU providers 104 RFC providers 98 SSM configuring objects in 111 connection 95 integration, customizing 146 reports for, customizing 147 SSO existing Dimensions CM installations 30 new Dimensions CM installations 30 SSO authentication in RESTgrid widgets 44 stages
CMS-XML VM I-Net users can no longer update archives after their first SSO token expired
... configured to use SSO ( Single Sign On ) may find ... ... logs into an SSO -enabled PDB ... The SSO token that is ... The user performs some actions involving a File Server-based archive, logs off and goes home. The next day, more than 8 hours after the first SSO token has expired, the user logs into the same PDB again. The user can see the projects and files just fine, but any attempt to update a file (check out, check in, label, lock, etc.) will fail with an Internal error 201
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs