Using SSL with Rich UI applications

When the HTML file that EGL generates for your Rich UI application is requested, a connection is made between the browser and the server to which your Rich UI application (including the EGL Rich UI Proxy) was deployed. Whenever a Web service is invoked in your Rich UI application, the EGL Rich UI Proxy creates a new connection between its server and the one on which the Web service is deployed. These connections are independent of one another and can use different protocols.

Requesting an HTML file with the SSL protocol (HTTPS) results in an SSL connection between the browser and server. If you use JEE authentication to secure an HTML file or the EGL Rich UI Proxy, require SSL to protect the user id and password from eavesdroppers as they are transmitted between the browser and server. When you use JEE authentication, to require SSL for the request, set the user data constraint in the web.xml to INTEGRAL or CONFIDENTIAL.

When you use custom authentication, you have various options to require HTTPS for the HTML file request. For instance, you can configure your Web server to redirect all HTTP requests to HTTPS. To redirect a specific HTML request, consider purchasing or writing a Java™ redirect filter, which you can specify on the Filters tab of your web.xml. You can use these filters to redirect certain HTTP requests to their HTTPS equivalent.

When a Web service is invoked with the SSL protocol, the EGL Rich UI Proxy creates a new SSL-enabled connection between its server and the one on which the Web service is deployed. When you secure Web services with HTTP basic authentication, require SSL to protect the user id and password during transmission. To require SSL for the request, set the user data constraint in the web.xml of the Web service project to INTEGRAL or CONFIDENTIAL. After you require SSL, invoke the Web service by using the HTTPS protocol.

When you invoke a secure Web service with SSL, ensure that the Rich UI application also uses the SSL protocol to protect the user id and password in the channel between the browser and server.


Feedback