Configuring Single Signon

To have the ENOVIA products work in a Single Signon (SSO) environment, a Single Signon server must be installed and configured.

The Collaboration server installations include both the framework.properties file used to configure ENOVIA products, and the web.xml file used in J2EE implementations. The web.xml file tells the server to look to the installation directory for framework.properties, but it can itself include the very property settings as parameters. To remove the dependency of the J2EE archive files on this external file, you should add all settings to web.xml instead of framework.properties. If a property is set in both framework.properties and web.xml, the value in web.xml is used. See the Live Collaboration Web Application Deployment Guide for details.

  1. Open the web.xml file for editing.

  2. Use these properties to bypass the emxLogin.jsp and emxLogout.jsp pages: 

    ematrix.sso.logout.url=URL
    ematrix.sso.absolute.logout.url=URL

    Use the first property to specify a relative path to the URL, use the second to specify an absolute path. Only enter a value for one of these properties. If you enter a value for ematrix.sso.logout.url, that value is used. The ematrix.sso.absolute.logout.url property is only used if the first property is not set.

  3. Save the web.xml file.

  4. To bypass the standard logout behavior (the default Logout button on the toolbar calls emxLogout.jsp):

    1. Remove the AEFLogoutToolbar command from the global toolbar (AEFGlobaltoolbar menu object).
    2. Add a custom logout command that points to a custom JSP that performs the SSO logout (calling the SSO software's APIs) and forwards users to another main page from which they can log back in.

      To create a new logout command, clone the AEFLogoutToolbar and change the href parameter to point to your custom JSP. For details on configuring global toolbar commands, see Menus and Toolbars.