Customizing Login Pages, Logout Pages, and Messages
67
n
ov
do
cx (e
n)
16
Ap
ril 20
10
1d
Leave the
Identifies User
option enabled, and configure the user store option according to
your needs.
1e
In the
Properties
section, click
New
, then specify the following values:
Property Name:
Query
Property Value:
(objectclass=person)(mail=%Ecom_User_ID%)
This property is defined so that it queries the user store for the attribute you want to use
rather than the cn attribute (in this case, the mail attribute of the person class). Change
to the name of the attribute in your user store that you want to use for the user
identifier.
The
%Ecom_User_ID%
variable is the default variable name on the login page. You can
change this to something like
%EMail_Address%
if you also change the value in your
custom login page.
For more information on how to use this property, see
“Query Property” on page 120
.
1f
In the
Properties
section, click
New
, then specify the following values:
Property Name:
JSP
Property Value:
<filename>
Replace
<filename>
with the name of the custom
login.jsp
page you are going to create
so that the page prompts the user for an e-mail address rather than a username. This must
be the filename without the JSP extension. For example, if you name your file
email_login.jsp
, then you would specify
email_login
for the property value.
1g
Click
OK
.
2
Create a contract that uses this method:
2a
Click
Contracts
>
New
.
2b
Select the method you just created.
2c
Configure the other options to fit your requirements.
If you are creating multiple custom login pages with customized credentials, you might
want to use the URI to hint at which custom
login.jsp
file is used with which custom
nidp.jsp
file. For example, the following URI values have the filename of the login page
followed by the name of the custom
nidp.jsp
page:
login1/custom1
login2/custom2
login3/custom3
For information on configuring the other options for a contract, see
Section 3.4,
“Configuring Authentication Contracts,” on page 124
.
2d
Update the Identity Server.
3
Copy the
login.jsp
file and rename it. The JSP files are located on the Identity Server in the
following directory:
Linux:
/var/opt/novell/tomcat5/webapps/nidp/jsp
Windows Server 2003:
\Program Files\Novell\Tomcat\webapps\nidp\jsp
Windows Server 2008:
\Program Files (x86)\Novell\Tomcat\webapps\nidp\jsp
4
(Conditional) If you modified the
%Ecom_User_ID%
variable, find the string in the file and
replace it with your variable.
Summary of Contents for ACCESS MANAGER 3.1 SP2 - README 2010
Page 4: ...4 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 12: ...12 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 158: ...158 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 172: ...172 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 182: ...182 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 290: ...290 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 362: ...362 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...
Page 374: ...374 Novell Access Manager 3 1 SP2 Identity Server Guide novdocx en 16 April 2010...