The procedures in this section assume that you have already deployed ProxyAuth.war into the Web container.
Creating the ProxyAuth sample JSP portlet
Launch Portal Studio. In a Web browser, enter
http://HOSTNAME.DOMAIN:8080/onepage/index.html
Log in to Portal Studio and select Build | Portlets.
Click the down arrow beside the New icon and select Aggregated Portlet.
In the Choose Portlet Type window, select JSP and click Next.
In the JSP Element Definition window, select Use Web Application, enter the following for ProxyAuth.war, then click Next.
WAR File To Upload – if you already deployed ProxyAuth.war in the Web container, you do not need to upload that file now. If you have not deployed ProxyAuth.war, specify the path to ProxyAuth.war and click Upload. There will be a success dialog when the upload has completed.
WAR File– ProxyAuth.war
Web App Display Name – ProxyAuth
Initial Resource – /ProxyAuth.jsp
Web App Qualified URL’s – select this option.
Single Sign-On Required– select this option.
When the Finish window appears, enter:
Portlet Name – ProxAuth.
Active/Iframe/Editable – select these options. Leave the remaining option on this line unselected.
Inline Portlet Clickthru – (only available when you select iFrame) select this option to enable links in this portlet to display inline; that is, links will not display in a separate pop-up window.
Title URL – leave blank.
Help URL – leave blank.
Category/Subcategory – accept the defaults.
Refresh Interval – accept the default.
Default Size – accept the default.
Shared By – leave blank.
Show Last Refresh – accept the default.
J2EE Roles – select roles from the Available Roles list and add them to the Assigned Roles list to define what roles can access this portlet.
User accounts with the roles in the Assigned Roles list
are the only user accounts that can access this portlet.
Description/Notes – add an optional description or note.
Click Finish.
When you return to the Portlet Manager window, select New from the Status menu. You should see the ProxAuth sample portlet listed in the detail view.
Right-click “ProxAuth” and select Approval Status | Approved.
Select Approved from the Status menu and verify that the ProxAuth sample portlet displays in the Approved detail view.
Creating a new page for the secured JSP portlet
Select Build | Pages from the Portal Studio left pane.
Click the New icon.
When the Page Builder window displays, click Add button and click on search. ProxAuth sample appears on the right-hand side.
Highlight ProxAuth and click Add.
When the Search window appears, click Search. The ProxAuth sample portlet displays in the Results pane, along with other existing portlets.
Click “ProxAuth” to select that portlet, then click Add. The portlet shows up in the Page Builder on the representation of the new page you are constructing.
Click Save As.
In the Save Page window, enter the following, then click OK.
Name – enter ProxAuth
Type – select Catalog.
Active – select this option.
Reg. Page Catalog – select this option.
The number you enter in the numeric (#) text field determines the position of the page in the list of available pages.
Page Catalog – do not select this option.
J2EE Roles – select roles from the Available Roles list and add them to the Assigned Roles list to define what roles can access this page.
User accounts with the roles in the Assigned Roles list
are the only user accounts that can access this page.
Click Close to exit the Page Builder window.
When you return to the Page Manager window, select New from the Status menu. You should see the ProxAuth page listed in the detail view.
Right-click ProxAuth and select Status | Approved.
Select Approved from the Status menu and verify that the ProxAuth page displays in the Approved detail view.
Adding the page to a user's page group
Launch Portal Interface. In a Web browser, enter:
http://HOSTNAME.DOMAIN:8080/onepage/index.jsp
Log in to Portal Interface.
Click Add Page.
If you have the required role, you see the ProxAuth page in the premade page list. Select that page and click Done.
The page should display, but the contents of the ProxyAuth portlet should indicate that the current user does not have any proxy authentication information for the target back end application.
