Siebel Security Guide > Web Single Sign-On Authentication > About Web Single Sign-On >

Web SSO Limitations

Because Web SSO deployments assume that user authentication and user management are the responsibility of the third-party security infrastructure, the following capabilities are not available, as Siebel Business Applications features, in a Web SSO environment:

• User self-registration
• Delegated administration of users
• Login forms
• Logout links or the Log Out menu item in the File application-level menu
• Change password feature (in Profile view of User Preferences screen)
• Anonymous browsing
• Switching from an anonymous user to a registered user while using the Shopping Cart

Verify that functionality you require does not rely on the capabilities in the previous list before you attempt to deploy such functionality in a Web SSO environment. For example, the Siebel eSales - Checkout Process workflow and user registration both make use of login forms.

Your Siebel Business Applications might require configuration changes to hide or disable the capabilities in the previous list. For information on hiding or disabling the capabilities listed, see Configuring Siebel Business Applications.

About Logging Out of a Web SSO Environment

Because Siebel Business Applications users in a Web SSO environment cannot use logout features, such users must end the application session by closing the browser window. In Microsoft Internet Explorer, do this by navigating to the File menu and choosing the Close menu item, or by clicking X in the top-right corner of the window.

For Siebel Business Applications that use high interactivity mode, either method of closing the browser window in a Web SSO environment causes the AOM to terminate the task (thread) for the user's session immediately.

For Siebel Business Applications that use standard interactivity mode, closing the browser window using either method in a Web SSO environment does not terminate the user's session until the session timeout (SessionTimeout) has been reached. However, if you are using a third-party single sign-on product, for example, Oracle Enterprise Single Sign-On, the user session is terminated when the browser window is closed.

The SessionTimeout parameter is located in the eapps.cfg file, on the SWSE. For more information about this parameter, see Parameters in the eapps.cfg File.

Related Topic

About Web Single Sign-On