Novell ACCESS MANAGER 3.1 SP1 - IDENTITY SERVER Manual page 43

For more information about setting property values, see
Common Class Properties," on page
1f (Conditional) If you created multiple custom login pages, repeat
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
"Troubleshooting Tips for Custom Login Pages," on page
Adding Logic to the main.jsp File
You can modify the
main.jsp
Identity Server must be running 3.1 SP1 or later to use this feature. Be aware of the following:
The file cannot be renamed, so any modifications you make to this file can be lost
main.jsp
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.
Modifying the
main.jsp
Modifying the
main.jsp
You can create multiple customized
, and
custom2.jsp
You can create multiple customized
For example:
login1.jsp: Configured to request username and password.
login2.jsp: Configured to request username, email, and password.
login3.jsp: Configured to request email and password.
With this type of configuration, you must create three different authentication contracts with an
authentication method with a JSP property defined for each of them. These contracts require the
types of values listed in the table below. The URI is defined so that it reflects the custom
and the custom
nidp.jps
90.
file and use the contract URI to specify the login page to display. The
file requires knowledge of JSP programming and if/else statements.
file allows you to have the following type of configuration:
nidp.jsp
.
custom3.jsp
login.jsp
that are used by the contract.
Section 2.2.2, "Specifying
Step 1b
Section 1.3.3,
47.
pages. For example:
custom1.jsp,
pages that request different login credentials.
Configuring an Identity Server
through Step 1e
login.jsp
43