Changing the login and logout pages | HCL Digital Experience
By default, when unauthenticated users attempt to access the myportal
page, they get redirected to the
login page to provide a user name and password. When using a WebSEAL or Computer Associates eTrust SiteMinder TAI for
authentication, you no longer need to use the HCL Digital Experience login
page. Instead, the login icon should point to the protected portal page.
About this task
Complete the following steps to change the login and logout pages:
Procedure
- Locate the
theme files that contain the
login and logout links. The files that contain the login and logout
links can be different, depending on the theme. In more recent themes,
these links might be located in Default.jsp.
In older themes, the links might be located in banner.jspf.Finding theme resources: See the Location of theme resources link in the Related section.
- Create a backup copy of the theme file before proceeding.
- Open the theme file and locate the section for the login button.
- Replace the login button
anchor tag that is not commented
out with the following JSP fragment:
<%-- comment this to enable screen login --%> <%-- loginOnClick is provided so the client-side aggregation theme can add this link without creating a different copy of this file. --%> <portal-logic:if loggedIn="no"> <c:if test="${empty loginOnClick}"> <li class="wptheme-toolbar-last"><a href='<portal-navigation:url home="protected" screen="Home"/>' <%=bidiDirAttr%>><portal-fmt:text key="link.login" bundle="nls.engine"/></a></li> </c:if> </portal-logic:if> --%>
Note: The previous example uses the 'portal-fmt:' prefix to designate JSP tags from the tag library in portal.tld. Your custom JSPs might use a different tag prefix. - Touch the Default.jsp file after editing any JSP files and before any restart. This updates the timestamp on the file to the current time and will signal a recompile of Default.jsp to incorporate the edit changes from other JSP files. Type: touch Default.jsp. An alternative is to edit (open and save) Default.jsp, which has the same effect as the touch command.
- Optional:
Redirect the browser to navigate to the logoff page of the external security manager (ESM)
after the HCL Portal logoff command executes. Learn how to
invalidate the single sign on session of the ESM by reviewing the documentation provided by the ESM
relating to logoff pages.
- Security Access Manager WebSEAL provides http://webseal/pkmslogout as a special URL to terminate the WebSEAL single sign on session
- In eTrust SiteMinder, the Web Agent configuration object contains a property named LogoffUri where you can supply a URL to terminate the eTrust SiteMinder login session
Complete the following steps to enable HCL Portal to execute the external security manager logoff URL after completing its logoff command: