Customizing Login Pages, Logout Pages, and Messages
73
n
ov
do
cx (e
n)
16
Ap
ril 20
10
Property Value:
custom1
The property value for the JSP property is the name of the custom login file without the
JSP
extension. Replace
custom1
with the name of your custom login file. This property
determines which login page is displayed when this method is used. The filename cannot
contain
nidp
as part of its name.
1f
Click
OK
.
For more information about setting property values, see
Section 3.2.2, “Specifying
Common Class Properties,” on page 120
.
1g
(Conditional) If you created multiple custom login pages, repeat
Step 1b
through
Step 1e
for each page.
2
For each method that you modified for a custom login page, create a contract:
2a
Click
Contracts
, then click
New
.
2b
Fill in the fields to fit the needs of the resource, but make sure to assign the custom
method as the method for the contract.
2c
Click
Next
, configure a card for the contract, then click
Finish
.
3
Update the Identity Server.
4
For each resource that you have created a custom login page, assign that resource to use the
contract that is configured to display the appropriate login page:
4a
Click
Devices
>
Access Gateways
>
Edit
>
[Reverse Proxy Name]
>
[Proxy Service
Name]
>
Protected Resources
.
4b
For each protected resource that you have created a custom contract for, select the
protected resource, then configure it to use the custom contract.
5
Update the Access Gateway.
6
(Conditional) If the custom page does not display correctly, see
Section 2.1.3,
“Troubleshooting Tips for Custom Login Pages,” on page 77
.
Adding Logic to the main.jsp File
You can modify the
main.jsp
file and use the contract URI to specify the login page to display. The
Identity Server must be running 3.1 SP1 or later to use this feature. Be aware of the following:
The
main.jsp
file cannot be renamed, so any modifications you make to this file can be lost
whenever you upgrade the Identity Server. During the upgrade, you must select to restore
custom files or you must restore your modified file after the upgrade. If this is the only JSP file
that you modified that uses an Identity Server name, it is probably best to manually restore this
file after an upgrade.
Modifying the
main.jsp
file requires knowledge of JSP programming and if/else statements.
Modifying the
main.jsp
file allows you to have the following type of configuration:
You can create multiple customized
nidp.jsp
pages. For example:
custom1.jsp,
custom2.jsp
, and
custom3.jsp
.
You can create multiple customized
login.jsp
pages that request different login credentials.
For example:
login1.jsp:
Configured to request username and password.
login2.jsp:
Configured to request username, email, and password.
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...