Novell ACCESS MANAGER 3.1 SP2 - README 2010, Manual

Page: 69 / 374

Customizing Login Pages, Logout Pages, and Messages 69
n
ov
do
cx (e
n)
16
Ap
ril 20
10
2 Add the custom branding and any other content you require to the file.
3 To modify the credentials, see “Customizing the Credential Frame” on page 66 .
4 Repeat Step 1 through Step 3 for each resource that requires unique branding.
5 Copy the files to each Identity Server in the cluster.
6 Back up your customized files.
7 (Optional) To view a sample custom page with these modifications, see Section 2.4.3, “Custom
3.1 login.jsp File,” on page 95 .
8 Continue with “Using Properties to Specify the Login Page” on page 72 .
Modifying the 3.0 Login Page
If you need a login page that doesn’t use iframes, you can use the 3.0 login page as the starting file
for your custom login page.
Figure 2-3 illustrates the default look and feel of this page.
Figure 2-3
Access Manager 3.0 Default Login Page
You can change the Novell branding and modify the credential prompts.
 “Modifying the Branding in the 3.0 Login Page” on page 69

“Modifying the Credentials in the 3.0 Login Page” on page 70
Modifying the Branding in the 3.0 Login Page
1 Copy the
/var/opt/novell/tomcat4/webapps/nidp/jsp/login.jsp
file from your 3.0
Identity Server and rename it.
If you do not have a 3.0
login.jsp
file, copy the modified version of this file from
“ Modifications Required for a 3.0 Login Page ” in the Novell Access Manager 3.1 SP2
Installation Guide to a true text editor. Delete all the extra line breaks.
2 (Conditional) If you are using the file from your 3.0 Identity Server, modify it so that it can
compile on a 3.1 Identity Server. For instructions, see “
Modifications Required for a 3.0 Login
Page ” in the Novell Access Manager 3.1 SP2 Installation Guide .
3 Replace the Access Manager 3.0 Login string:
3a Find the following line in the file:
<div id="title"><b><%=handler.getResource(JSPResDesc.TITLE)%></b></
div>