15.1 Maintaining Customized JSP Files for Identity Server

Access Manager contains a default user portal and a set of default login pages from Access Manager 4.2 onwards. The new login pages have a different look and feel compared to the default login pages of Access Manager 4.1 or prior. If you have customized the legacy user portal, you can maintain the customized JSP pages in the following two ways:

15.1.1 Using Customized JSP Pages from Access Manager 4.1 or Prior

  1. Before upgrade, create a copy of all JSP files inside the /opt/novell/nids/lib/webapp/jsp directory and place the copy somewhere else.

    WARNING:The upgrade overwrites all existing JSP files.

  2. Upgrade Identity Server.

  3. Create an empty folder legacy.

  4. Add the legacy folder to Identity Server in the/opt/novell/nids/lib/webapp/WEB-INF/ directory using Advanced File Configurator.

    For information about how to add a folder, see Adding Configurations to a Clusterin the NetIQ Access Manager 5.0 Administration Guide.

    NOTE:If you do not create the legacy folder, Access Manager uses the logic of the default new login pages.

  5. Add all backed up JSP files into the /opt/novell/nids/lib/webapp/jsp directory using Advanced File Configurator. For information about how to add files, see Adding Configurations to a Clusterin the NetIQ Access Manager 5.0 Administration Guide.

  6. Refresh the browser to see the changes.

15.1.2 Using Customized JSP Pages from Access Manager 4.1 or Prior and Enabling the New Access Manager Portal

  1. Before upgrade, create a copy of all JSP files inside the /opt/novell/nids/lib/webapp/jsp directory and place the copy somewhere else.

    WARNING:The upgrade overwrites all existing JSP files.

  2. Upgrade Identity Server.

  3. Create an empty folder legacy.

  4. Add the legacy folder to Identity Server in the/opt/novell/nids/lib/webapp/WEB-INF/ directory using Advanced File Configurator.

    For information about how to add a folder, see Adding Configurations to a Clusterin the NetIQ Access Manager 5.0 Administration Guide.

    NOTE:If you do not create the legacy folder, Access Manager uses the logic of the default new login pages.

  5. Open customized nidp.jsp and content.jsp files and make the following changes in both files:

    For information about how to modify a file, see Adding Configurations to a Clusterin the NetIQ Access Manager 5.0 Administration Guide.

    1. In the top Java section of the JSP file, find the ContentHandler object that looks similar to the following:

      ContentHandler handler = new ContentHandler(request,response);

    2. In the code, add the following Java line under ContentHandler:

      boolean bGotoAlternateLandingPageUrl = handler.gotoAlternateLandingPageUrl();

    3. Find the first instance of <script></script> in the JSP file that is not <script src></script>, then insert the following line in to the JavaScript section between the <script></script> tags:

      <% if (bGotoAlternateLandingPageUrl) { %>
        document.location = "<%=handler.getAlternateLandingPageUrl()%>";
<%  } %>

      This redirects control to the default portal page that contains appmarks.

  6. Refresh the browser to see the changes.