Saturday February 17, 2007 Communications Express Deployments in 6.3
A big change that we are very excited about is coming in our upcoming Communications Express 6.3. One of the biggest features of this release is the greatly simplification of installation and configuration of Communications Express. In previous release, this has been a cumbersome installation. The main reason for this was the complexity of configuring the Single-Sign-On (SSO) correctly. In these releases, we needed to configure SSO for both authentication between Communications Components (i.e. the UWC Servlet and the Webmail mshttpd) and for authentication to 3rd party web products (such as Sun Java Portal Server). The figure below demonstrates the complexity.
In the pre-6.3 releases, the SSO between the UWC Servlet and the Messaging Express Multiplexor (MEM) required that the session information be stored on the user's web browser. This session information was stored as a cookie for that domain. This cookie was created either by Sun Java Access Manager or by Communications Express' Messaging SSO (aka Trusted Circle). This required careful configuration of the SSO information in both
1) uwcauth.properties file in UWC and 2) the configutil attributes for messaging server.
In Communications Express 6.3, things get a lot easier for SSO. We have moved the MEM behind the UWC Servlet. This prevented the user's web browser from ever connecting directly to the MEM's mshttpd process. This eliminated the need for our session cookies for our internal single-sign-on. If you want to integrate with 3rd party Web Applications, you still have the option of using Access Manager. NOTE: Access Manager will still be required for Delegated Admin.
Comments [2]
Comments are closed for this entry.
Posted by dk on February 22, 2007 at 07:52 PM PST #
Posted by Jonathan Hawkins on February 22, 2007 at 11:45 PM PST #