Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Page 3
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
This guide is intended for Access Manager administrators who are new to the product.
novdocx (en) 17 September 2009
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of the Access Manager Quick Start Guide, visit the Novell Access
Manager Documentation Web site (http://www.novell.com/documentation/novellaccessmanager).
Novell Access Manager 3.1 SP1 SSL VPN Server Guide
Novell Access Manager 3.1 SP1 Agent Guide
Documentation Conventions
In Novell
®
documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
®
A trademark symbol (
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
About This Guide7
Page 8
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux* or UNIX*, should use forward slashes as required by your software.
novdocx (en) 17 September 2009
8Novell Access Manager 3.1 SP1 Quick Starts
Page 9
1
A
Installation Quick Start
A basic Access Manager installation has three Access Manager components (an Administration
Console, an Identity Server, and an Access Gateway), an LDAP server, and Web servers with
applications and data. Figure 1-1 illustrates a configuration where these components are installed on
separate machines.
Figure 1-1 Basic Installation
LDAP ServerIdentity Server
novdocx (en) 17 September 2009
1
dministration Console
Access Gateway
The Administration Console must be installed first. The other components can then be installed in
any order.
Section 1.1, “System Requirements,” on page 9
Section 1.2, “Administration Console,” on page 10
Section 1.3, “Identity Server,” on page 10
Section 1.4, “Linux Access Gateway,” on page 11
Section 1.5, “Verifying the Installation,” on page 11
Web Servers
1.1 System Requirements
Review the following sections in the Novell Access Manager 3.1 SP1 Installation Guide to ensure
that your machines or virtual images meet the installation prerequisites:
“Administration Console Requirements”
“Identity Server Requirements”
“Access Gateway Requirements”
Installation Quick Start
9
Page 10
1.2 Administration Console
What you need to know The username and password you want to use for the Access
Manager administrator.
This is your first installation of an Administration Console, so when
prompted, answer Yes for a primary installation.
You can create a failover environment by installing more than one
Administration Console. For more information, see “Clustering and
Fault Tolerance” in the Novell Access Manager 3.1 SP1 Setup Guide.
For more informationSee “Installing the Access Manager Administration Console” in the Novell
Access Manager 3.1 SP1 Installation Guide.
1.2.1 Linux Administration Console
novdocx (en) 17 September 2009
1 Use
2 At the Installation menu, select 1, then follow the prompts.
3 Answer yes to the primary installation prompt.
install.sh
to start the installation.
1.2.2 Windows Administration Console
1 Download the Windows file and execute it.
For software download instructions, see the “Novell Access Manager Readme” (http://
Each icon should contain the number one, if your component successfully imported into the
Administration Console.
If a component has not imported, click the link to the device. If a repair import option is
available, click this link. If it is not available, see “Troubleshooting Installation” in the Novell
Access Manager 3.1 SP1 Installation Guide.
novdocx (en) 17 September 2009
4 Before continuing with configuration, verify the following:
Use the
ping
command to verify that the DNS names for the Identity Server and the
Access Gateway are resolvable.
Make sure time is synchronized among your components.
12Novell Access Manager 3.1 SP1 Quick Starts
Page 13
2
A
Configuration Quick Start
A basic configuration has three Access Manager components (an Administration Console, an
Identity Server, and an Access Gateway), an LDAP server, and Web servers with applications and
data. Figure 2-1 illustrates a configuration where these components are installed on separate
machines.
Figure 2-1 Modules Required for a Basic Configuration
LDAP ServerIdentity Server
novdocx (en) 17 September 2009
2
dministration Console
Access Gateway
This section explains how to configure your system so that user in your LDAP server can log in and
access a protected resource on a Web server.
Section 2.1, “New Identity Server Cluster Configuration,” on page 13
Section 2.2, “First Reverse Proxy Configuration,” on page 16
Section 2.3, “Configuring the Protected Resource for Authentication,” on page 17
Web Servers
2.1 New Identity Server Cluster Configuration
This section explains how to add your Identity Server to a cluster and how to configure the cluster to
communicate with the LDAP server and use its authentication credentials.
Configuration Quick Start
13
Page 14
Table 2-1 Identity Server Configuration Information
What you need to knowExampleYour Value
LDAP server information:
DN of the administratorcn=admin,o=novell______________________
Password of the administrator novell
_______________________
novdocx (en) 17 September 2009
IP address of the LDAP
server
DN of the user containero=novell______________________
DNS name of the Identity Serveripda.test.novell.com______________________
Names you need to create:
Identity Server cluster nameidpa
User store nameUser Store_______________________
Replica nameUser Store Replica_______________________
Alias certificate nameUserStoreRoot_______________________
Organization information for the Identity
Server cluster:
For more information, see “Creating a Basic Identity Server Configuration” in the Novell Access Manager
3.1 SP1 Setup Guide.
10.10.10.16
______________________
______________________
1 In the Administration Console, click the Identity Servers task.
2 Click New Cluster.
3 Specify a name such as
In Tabl e 2-1,
idpa
is the Identity Server cluster name you created.
4 Configure the Base URL of the Identity Server, using the DNS name of the Identity Server:
http://idpa.test.novell.com:8080/nidp
In Tabl e 2-1, this is the DNS name of the Identity Server with a port and
5 Click Next, then configure the organization information.
Name:
Display name:
URL:
Access Manager
Access Manager 3
ipda.am3sp3.com
In Tabl e 2-1, these three fields are the organization information you created for the Identity
Server cluster.
6 Click Next, then configure the user store:
14Novell Access Manager 3.1 SP1 Quick Starts
idpa
, select your Identity Server, then click OK.
/nipd
.
Page 15
novdocx (en) 17 September 2009
Name:
In Tabl e 2-1,
Admin name:
User Store
User Store
cn=admin,o=novell
is the user store name you created.
In Tabl e 2-1, this is the DN of the administrator for the LDAP server.
Admin password:
Confirm password:
novell
novell
In Tabl e 2-1, these fields are the password for the administrator of the LDAP server.
Directory Type: Select a type from the drop-down menu.
7 In the Server replicas section, click New, then fill in the following fields:
Name:
In Tabl e 2-1,
IP Address:
User Store Replica
User Store Replica
10.10.10.16
is the name you created for the replica
In Tabl e 2-1, this is the IP address of the LDAP server.
Use secure LDAP connections: Select this option.
Auto import trusted root: Click this link, follow the prompts, and specify
UserStoreRoo
t for
the alias.
In Tabl e 2-1,
UserStoreRoo
t is the alias certificate name you created.
8 Click OK, then make sure the Validation Status of the replica displays a green check mark. If it
is red, you have a configuration error:
Check the distinguished name of the admin user, the password, and the IP address of the
replica.
Check for network communication problems between the Identity Server and the LDAP
server.
9 In the Search Contexts section, click New, then specify the following:
Search context:
o=novell
In Tabl e 2-1, this is the DN of the user container.
Scope:
Subtree
10 Click OK > Finish, then restart Tomcat as prompted.
11 Wait for the health status of the Identity Server to turn green, then verify the configuration:
11a Enter the Base URL of the Identity Server in a browser.
http://idpa.test.novell.com:8080/nidp
11b Log in using the credentials of a user in the LDAP server.
The user portal appears.
If the URL returns an error rather than displaying a login page, verify the following:
The browser machine can resolve the DNS name of the Identity Server.
The browser machine can access to the port.
Configuration Quick Start15
Page 16
2.2 First Reverse Proxy Configuration
This section explains how to create a reverse proxy to protect the name and IP address of your Web
server from being exposed to users. Section 2.3, “Configuring the Protected Resource for
Authentication,” on page 17 builds on this configuration and explains how to require authentication
to gain access to the Web server.
Table 2-2 Access Gateway Configuration Information
What You Need To KnowExampleYour Value
Name of the Identity Server clusteridpa_______________________
DNS name of the Access Gatewaylag.test.novell.com______________________
Web server information
IP address10.10.16.16______________________
DNS namedigital.test.novell.com______________________
For more information, see “Configuring the Access Gateway” in the Novell Access Manager 3.1 SP1
Setup Guide.
1 In the Administration Console, click the Access Gateways task.
2 Click Edit, then click Reverse Proxy/Authentication.
3 Configure a reverse proxy:
In the Authentication Settings section, select
idpa
from the drop-down list.
In Tabl e 2-2, this is the name of the Identity Server cluster.
In the Reverse Proxy section, click New, specify
In Tabl e 2-2,
DigitalAirlines
is the reverse proxy name you created.
DigitalAirlines
, then click OK.
4 To configure a proxy service, click New in the Proxy Service section, then fill in the following
fields:
Proxy Service Name:
DA
In Tabl e 2-2, DA is proxy service name you created.
Published DNS Name:
In Tabl e 2-2, this is the DNS name of the Access Gateway.
Web Server IP Address:
In Tabl e 2-2, this is the IP address of the Web server.
Host Header: Select the Web Server Host Name from the drop-down list.
Web Server Host Name:
16Novell Access Manager 3.1 SP1 Quick Starts
lag.test.novell.com
10.10.16.16
digital.test.novell.com
Page 17
5 Click OK, then configure a protected resource.
Click the Protected Resource tab.
In the Protected Resource section, click New, then specify
In Tabl e 2-2,
In the URL Path section, examine the path. It should be set to /* which matches everything
on the Web server.
6 Click OK to save the configuration.
7 Click the Access Gateways task, then click Update.
Wait for the health status to turn green. If it doesn’t turn green, click the Health icon to discover
the cause.
If the Access Gateway cannot connect to the Web server, verify the IP address of the Web
server.
everything
is the protected resource name you created.
everything
.
novdocx (en) 17 September 2009
Use the
server and the Identity Server.
Verify that the Access Gateway can resolve the DNS name of the Identity Server.
For other problems, see “Monitoring the Health of an Access Gateway” in the Novell
Access Manager 3.1 SP1 Access Gateway Guide.
8 Click the Identity Servers task, then click Update.
9 To test that the Access Gateway is protecting the Web server, open a browser and enter the
following URL:
http://lag.test.novell.com:80/
The first page of the Web server is displayed. If you get an error, verify the following:
Check the times on the Access Gateway and the Identity Server. Their times need to be
synchronized.
Verify that the browser machine can resolve the DNS name of the Access Gateway.
ping
command to verify that the Access Gateway can communicate with the Web
2.3 Configuring the Protected Resource for
Authentication
This section explains how to configure the Access Gateway so that users are prompted to log in
when accessing the protected resource.
1 To return to the protected resource, click Access Gateways > Edit > DigitalAirlines > DA >
Protected Resources > everything.
2 For the Contract option, select Name/Password Form from the drop-down list.
If the list is empty, you have not selected an Identity Server cluster configuration for the Access
Gateway. See Step 3 on page 16.
3 Click OK to save the configuration.
4 Click the Access Gateways task, then click Update.
5 To test that accessing the resource now requires authentication, open a browser, then enter the
URL to your protected resource:
http://lag.test.novell.com:80/
Configuration Quick Start17
Page 18
When you are prompted for login credentials, use a name and a password from a user on the
LDAP server.
If you receive an error, verify the following:
The Identity Server can resolve the DNS name of the Access Gateway.
The Access Gateway can resolve the DNS name of the Identity Server.
Time is synchronized between the Identity Server and the Access Gateway.
For other problems, see “General Authentication Troubleshooting Tips” in the Novell Access
Manager 3.1 SP1 Identity Server Guide.
novdocx (en) 17 September 2009
18Novell Access Manager 3.1 SP1 Quick Starts
Page 19
3
SSL Configuration Quick Start
Access Manager has five communication channels that can be configured for SSL. Figure 3-1
illustrates these channels.
Figure 3-1 Potential SSL Communication Channels
LDAP ServerIdentity Server
1
SSL
3
SSL
SSL
2
Access Gateway
Web Servers
novdocx (en) 17 September 2009
3
SSL
Browser
The channels need to be configured according to their numeric values. You need to configure SSL
between the Identity Server and the LDAP server before you configure SSL between the Identity
Server and the browsers. The Identity Server must be configured for SSL before you configure the
channel between the Access Gateway and the Identity Server for SSL.
The following procedures assume that you want to set up a new system using certificates created by
the Access Manager Certificate Authority. To modify an existing system to use SSL, see “Enabling
SSL Communication” in the Novell Access Manager 3.1 SP1 Setup Guide. To use certificates signed
by an external CA, see “Using Externally Signed Certificates” in the Novell Access Manager 3.1
SP1 Setup Guide.
This section describes the following tasks:
Section 3.1, “Configuring a New Identity Server Cluster with SSL,” on page 19
Section 3.2, “Configuring a New Access Gateway for SSL,” on page 22
SSL
54
3.1 Configuring a New Identity Server Cluster
with SSL
This section explains how to add your Identity Server to a cluster, how to configure the cluster to use
SSL, and how to configure the cluster to communicate with the LDAP server so users can access
their authentication credentials.
SSL Configuration Quick Start
19
Page 20
What You Need to KnowExampleYour Value
LDAP server information:
DN of the administratorcn=admin,o=novell_______________________
Password of the administrator novell_______________________
novdocx (en) 17 September 2009
IP address of the LDAP
server
DN of the user containero=novell_______________________
DNS name of the Identity Serveripda.test.novell.com_______________________
Certificate nameipda_test________________________
Certificate subject fields:
Common name ipda.test.novell.com________________________
For more information, see “Creating a Basic Identity Server Configuration” in the Novell Access Manager
3.1 SP1 Setup Guide.
1 In the Administration Console, click Access Manager > Identity Servers.
2 Click New Cluster.
3 Specify a name such as
idpa
, select your Identity Server, then click OK.
4 Configure the Base URL of the Identity Server, using the DNS name of the Identity Server:
https://idpa.test.novell.com:8443/nidp
5 On the SSL Certificate line, click the Select Certificate icon, then click Replace.
6 In the Replace box, click the Select Certificate icon.
20Novell Access Manager 3.1 SP1 Quick Starts
Page 21
7 On the Certificates page, click New.
8 Select Use local certificate authority.
9 Fill in the following fields:
Certificate name:
idpa_test
Signature algorithm: Accept the default.
Valid from: Accept the default.
Months valid: Accept the default.
Key size: Accept the default.
10 Click the Edit icon on the Subject line.
11 Fill in the following fields:
Common name:
Organizational unit:
idpa.test.novell.com
o=novell
novdocx (en) 17 September 2009
Organization:
City or town:
State or province:
Country:
test
Provo
UT
US
12 Click OK twice.
13 Verify that the new certificate is selected, then click OK.
14 In the Replace box, click OK, then click Close.
15 To configure the organization information, click Next, then fill in the following fields:
Name:
Display name:
URL:
Access Manager
Access Manager 3
ipda.am3sp3.com
16 Click Next, then configure the user store:
Name:
Admin name:
Admin password:
Confirm password:
User Store
cn=admin,o=novell
novell
novell
Directory Type: Select a type from the drop-down menu.
17 In the Server replicas section, click New, then fill in the following fields:
Name:
IP Address:
User Store Replica
10.10.10.16
Use secure LDAP connections: Select this option.
Auto import trusted root: Click this link, follow the prompts, and specify
the alias.
UserStoreRoo
SSL Configuration Quick Start21
t for
Page 22
18 Click OK, then make sure the Validation Status of the replica displays a green check mark. If it
is red, you have a configuration error:
Check the distinguished name of the admin user, the password, and the IP address of the
replica.
Check for network communication problems between the Identity Server and the LDAP
server.
19 In the Search Contexts section, click New, then specify the following:
Search context:
Scope:
Subtree
o=novell
20 Click OK, click Finish, then restart Tomcat as prompted.
21 Wait for the health status of the Identity Server to turn green, then verify the configuration:
21a Enter the Base URL of the Identity Server in a browser.
https://idpa.test.novell.com:8443/nidp
21b Log in using the credentials of a user in the LDAP server.
The user portal appears.
novdocx (en) 17 September 2009
If the URL returns an error rather than displaying a login page, verify the following:
The browser machine can resolve the DNS name of the Identity Server.
The browser machine can access port 8443.
3.2 Configuring a New Access Gateway for SSL
This section explains how to create a reverse proxy to protect the name and IP address of your Web
server from being exposed to users, how to require SSL between the browsers and the reverse proxy,
and how to require authentication to gain access to the Web server.
What You Need to KnowExampleYour Value
Name of the Identity Server clusteridpa_______________________
DNS name of the Access Gatewaylag.test.novell.com______________________
Web server information
IP address10.10.16.16______________________
DNS namedigital.test.novell.com______________________