Troubleshooting Tips For Custom Login - Novell ACCESS MANAGER 3.1 SP2 - IDENTITY SERVER GUIDE 2010 Manual

// or a method definition that should be displayed
// as the main jsp here?
if (hand.contractDefinesMainJSP())
{
%>
<%@ include file="mainRedirect.jsp" %>
<% }
else if(strContractURI != null && strContractURI.equals("login1/
custom1"))
{
%>
<%@ include file="custom1.jsp" %>
<% }
else if(strContractURI != null && strContractURI.equals("login2/
custom2"))
{
%>
<%@ include file="custom2.jsp" %>
else if(strContractURI != null && strContractURI.equals("login3/
custom3"))
{
%>
<%@ include file="custom3.jsp" %>
<% } // This is the jsp used by default
else
{
%>
<%@ include file="nidp.jsp" %>
<% } %>
3d Copy the modified
4 Back up your customized files.
5 For each resource that you have created a custom login page for, assign that resource to use the
contract that is configured to display the appropriate login page:
5a Click Devices > Access Gateways > Edit > [Reverse Proxy Name] > [Proxy Service
Name] > Protected Resources.
5b For each protected resource that you have created a custom contract for, select the
protected resource, then configure it to use the custom contract.
5c Update the Access Gateway.
6 (Conditional) If the custom page does not display correctly, see
"Troubleshooting Tips for Custom Login Pages," on page
2.1.3 Troubleshooting Tips for Custom Login Pages
If your custom login page does not display or generates an error message, use the following
procedure to discover the root cause:
1 Set the Application option of Component File Logger Levels to debug, update the Identity
Server, attempt to log in, then view the log file.
file to each Identity Server in your cluster.
main.jsp
Customizing Login Pages, Logout Pages, and Messages
Section 2.1.3,
77.
77