The Secure Web Proxy has been enhanced to allow integration into Portal Interface as a portlet. The Secure Web Proxy should be deployed and configured as a standalone Web application on EAServer, leaving the application server connection information blank within swp.properties. Once you verify that the Secure Web Proxy is configured and functioning standalone, you can create a portlet using Web Studio that includes a JSP element including the desired Secure Web Proxy content. To create this type of portlet, set the following parameters in the JSP Element Definition window:
In the JSP Element Definition window, select Use Web Application, click Browse to the right of the WAR File to Upload field and navigate to select %SYBASE%\Security\lib\webproxy.war on Windows and $SYBASE/Security/lib/webproxy.war on UNIX.
When you locate the WAR file, select the file and click Open in the Choose File dialog box.
When the path to the WAR file displays in the JSP Element Definition window, click Upload. When the confirmation that the WAR file was uploaded successfully displays, click OK. The WAR File and Web App Display Name fields are automatically filled in.
In the Initial Resource field, enter:
proxy/[application name]/
Replace [application name] with the configured application’s name from swp.properties that you want to have appear in the portlet.
Select Single Sign On Required and 302 Redirect.
When you are satisfied with your entries, click Next.
Once this configuration is complete, you should see the appropriate content appear in the preview window.
Enter an element name, then click Finish. You return to the Portlet Builder.
Regardless of the element type, the procedure to save the element and portlet is the same. See“Saving portlets” for instructions.
See security.log and the various Jaguar logs for error and diagnostic information. See also the Enterprise Security Administration Guide.
| Copyright © 2004. Sybase Inc. All rights reserved. |
|
|
