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 Cookie Authentication and Using Web Queries in External Applications
Cookie Authentication and Using Web Queries in External Applications
CMS-XML How to make cookies like JSESSIONID secure if HTTPS encryption/decryption is handled by an external device, like an F5 load balancer
How to make cookies like JSESSIONID secure if HTTPS encryption/decryption is handled by an external device, like an F5 load balancer
PDF Untitled Document
... 1.2 Cookie Authentication.. ... 1 Basic/ Cookie /Internal Checking ................. ... ............. 2 2.2.2 Basic/ Cookie /External Checking ................................ 2 2.2.3 Basic/ Cookie /LDAP . ...
TEXT ReadmeVMS.txt
MERANT PVCS VM SERVER 6.7 README File This file contains issues or known problems in this release. TABLE OF CONTENTS 1.0 WHAT'S NEW IN THIS RELEASE 1.1 Support for New Platforms 2.0 INSTALLATION ISSUES 2.1 Internet Explorer Setup for Client Installations 2.2 Netscape Setup for Client Installations 2.3 Installing the VM I-NET Client Applet on Win32 2.4 Installing the VM I-NET Client Applet on UNIX 2.5 Do Not Disable Cookies 2
CMS-XML Enabling SSO across browser instances
SSO tokens are not persisted across multiple browser instances and this is by design. Persistent Cookies are not secure when computers are shared by users. The below workaround will allow you to relax the restriction if you explicitly choose to.
CMS-XML Default state change history to "Show All" rather than "Show less"
The State Change History is controlled via a cookie and defaults to there being no cookie set and therefore displaying it as "Show Less" - per displayed below.
CMS-XML Do users authenticate automatically to Portfolio Edge?
In certain circumstances, yes. When the user first goes to the web site and logsin, we store their username in a cookie . The next time they go to the web page, we compare that username to their windows account name.
CMS-XML Repeated Calls to Java Side of Work Center
This occurs when the JSESSIONID cookie is not sent on these repeat requests to /commonsvc (the Java side of Work Center). This can occur if you attempt an HTTPS connection to SBM (which sets the cookie as "Secure connections only") followed by an HTTP URL request for Work Center. The cookie is not sent because the connection is not secure over HTTP.
CMS-XML Pass through authentication via URL
a session cookie will not be created until you close/exit the browser. This cookie will not be deleted until you close the browser. This means that the URL will not work again until the browser is closed.
CMS-XML Can I launch AppScript from URL with sso user login?
When using SSO there's no way to do this. SBM has several authentication types available with increasing levels of security. SBM does support an authentication type that allows for login parameters on the URL (Form/URL/ Cookie ) but this does not work for all authentication types.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs