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:
Before upgrade, create a copy of all JSP files inside the jsp directory and place the copy somewhere else.
Linux: /opt/novell/nids/lib/webapp/jsp
Windows: \Program Files\Novell\Tomcat\webapps\nidp\jsp
WARNING:The upgrade overwrites all existing JSP files.
Upgrade Identity Server.
Create an empty folder legacy in Identity Server
Linux: /opt/novell/nids/lib/webapp/WEB-INF/legacy
Windows: \Program Files\Novell\Tomcat\webapps\nidp\WEB-INF\legacy
NOTE:If you do not create the legacy folder, Access Manager uses the logic of the default new login pages.
Copy your all backed up JSP files into the jsp directory.
Linux: /opt/novell/nids/lib/webapp/jsp
Windows: \Program Files\Novell\Tomcat\webapps\nidp\jsp
Refresh the browser to see the changes.
Before upgrade, create a copy of all JSP files inside the jsp directory and place the copy somewhere else.
Linux: /opt/novell/nids/lib/webapp/jsp
Windows: \Program Files\Novell\Tomcat\webapps\nidp\jsp
WARNING:The upgrade overwrites all existing JSP files.
Upgrade Identity Server.
Create an empty folder legacy in Identity Server
Linux: /opt/novell/nids/lib/webapp/WEB-INF/legacy
Windows: \Program Files\Novell\Tomcat\webapps\nidp\WEB-INF\legacy
NOTE:If you do not create the legacy folder, Access Manager uses the logic of the default new login pages.
Copy your all backed up JSP files into the jsp directory.
Linux: /opt/novell/nids/lib/webapp/jsp
Windows: \Program Files\Novell\Tomcat\webapps\nidp\jsp
Find the customized nidp.jsp and content.jsp files and make the following changes in both files:
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);
In the code, add the following Java line under ContentHandler:
boolean bGotoAlternateLandingPageUrl = handler.gotoAlternateLandingPageUrl();
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.
Save the file.
Repeat the steps for the second JSP file.
Refresh the browser to see the changes.