Understanding JSP Files

Access Manager supports two user interface layouts, legacy and latest. The legacy user interface is the user portal layout that was used before Access Manager 4.2. The latest user interface is the layout that got introduced in Access Manager 4.2. It is recommended to use the latest user interface because it is easy to use and includes enhanced features, such as appmarks.

To support these two user interface layouts, JSP files require different implementation and logic. A naming convention is introduced to distinguish those JSP files for both the user interfaces. Some JSP files do not require different implementation such as, saml2post.jsp, which follows the common naming convention.

To understand which JSP files to use for a specific user interface, some JSP files are classified into two different naming conventions and some JSP files have a common naming convention.

The following are naming conventions for the JSP files:

Convention	Description
<name>_legacy.jsp	Used for the JSP pages designed for the legacy user portal (the portal that does not contain the enhanced features). If you edit this type of file, the corresponding <name>.jsp file includes those changes. For example, login_legacy.jsp.
<name>_latest.jsp	Used for the JSP pages designed for the latest user portal (the portal that contains branding and appmark enhancements). If you edit this type of file, the corresponding <name>.jsp file includes those changes. For example, login_latest.jsp.
<name>.jsp	Used for JSP files that include the implementation based on the active user interface. This naming convention is also used for the JSP files that are not dependent on the active user interface. Hence, some JSP files do not have the corresponding <name>_legacy.jsp or <name>_latest.jsp files. For example, login.jsp. The login.jsp file will include the logic of either login_legacy.jsp or login_latest.jsp based on the active user interface. These type of JSP files do not require any modification.

Convention

Description

<name>_legacy.jsp

Used for the JSP pages designed for the legacy user portal (the portal that does not contain the enhanced features). If you edit this type of file, the corresponding <name>.jsp file includes those changes. For example, login_legacy.jsp.

<name>_latest.jsp

Used for the JSP pages designed for the latest user portal (the portal that contains branding and appmark enhancements). If you edit this type of file, the corresponding <name>.jsp file includes those changes. For example, login_latest.jsp.

<name>.jsp

Used for JSP files that include the implementation based on the active user interface. This naming convention is also used for the JSP files that are not dependent on the active user interface. Hence, some JSP files do not have the corresponding <name>_legacy.jsp or <name>_latest.jsp files.

For example, login.jsp. The login.jsp file will include the logic of either login_legacy.jsp or login_latest.jsp based on the active user interface.

These type of JSP files do not require any modification.

If the /opt/novell/nids/lib/webapp/WEB-INF/legacy folder exists, then the active user interface is the legacy layout. If the folder does not exist, the active user interface is the latest layout.

This section focuses on the latest layout as the active user interface. Therefore, only <name>_latest.jsp and <name>.jsp are used. If you find any JSP file with the <name>_legacy.jsp naming convention, you must remove the /opt/novell/nids/lib/webapp/WEB-INF/legacy folder from each Identity Server deployment.