Novell IDENTITY ASSURANCE SOLUTION INSTALLATION GUIDE

Identity Assurance Solution 3.0.2 Installation Guide

Novell
Identity Assurance Solution

novdocx (en) 24 April 2008

3.0.2

May 12, 2008

www.novell.com

INSTALLATION GUIDE

Legal Notices

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.

novdocx (en) 24 April 2008

Copyright © 2007-2008 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.

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).

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.

novdocx (en) 24 April 2008

novdocx (en) 24 April 2008

Contents

About This Guide 7

1Overview 9

1.1 Identity Assurance Solution Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 Driver Overviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2.1 PIV Life Cycle Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.2.2 PIV Workflow Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.2.3 Enrollment Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.2.4 CMS Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.2.5 PACS Integration Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.3 Identity Assurance Solution Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.4 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2 Planning the Identity Assurance Solution Installation 17

novdocx (en) 24 April 2008

2.1 Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.1.1 Novell Identity Manager Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2.1.2 Identity Vault Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.3 User Enrollment/Biometric Capture Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.4 Card Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.5 Physical Access Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.6 User Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.7 Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.1.8 Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2 Preparing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2.1 Novell Products that Need to be Downloaded and Installed . . . . . . . . . . . . . . . . . . . 19

2.2.2 Third-Party Products that Need to be Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2.3 IAS CD Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.3 Contents of Each Identity Assurance Solution CD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.4 What's Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Installing Identity Assurance Solution 21

3.1 Installing the User Enrollment Biometric Capture Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2 Installing the Card Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.3 Installing the Physical Access Control System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.4 Installing the Identity Vault Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.4.1 Novell eDirectory 8.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.4.2 iManager 2.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.4.3 Novell Identity Manager 3.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.4.4 Novell Identity Manager 3.5.1 on Connected Systems . . . . . . . . . . . . . . . . . . . . . . . 23

3.4.5 Novell Enhanced Smart Card Method (NESCM) Server Component . . . . . . . . . . . . 23

3.5 Installing Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.5.1 PIV Life Cycle Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.5.2 PIV Workflow Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.5.3 Enrollment Driver for the Honeywell SmartPlus System . . . . . . . . . . . . . . . . . . . . . . 25

3.5.4 CMS Driver for ActivIdentity ActivID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.5.5 PACS Integration Driver for the Honeywell SmartPlus System. . . . . . . . . . . . . . . . . 28

3.6 Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Contents 5

3.7 Installing Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

3.7.1 Installing the Novell Client Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.7.2 Workstation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.8 What's Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4 Configuring Identity Assurance Solution 33

4.1 Configuring the Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.1.1 Configuring the PIV Life Cycle Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.1.2 Configuring the PIV Workflow Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4.1.3 Configuring the Enrollment Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.1.4 Configuring the Honeywell SmartPlus Enrollment System . . . . . . . . . . . . . . . . . . . . 39

4.1.5 Configuring the CMS Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4.1.6 Configuring the PACS Integration Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

4.1.7 (Optional) Using Designer to Customize Your Implementation . . . . . . . . . . . . . . . . . 43

4.2 Installing the User Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.2.1 Installing User Application for Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.2.2 Installing the IAS Digital Signature Applet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.2.3 Restarting the PIV Life Cycle Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.3 Configuring E-Mail Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4.4 What’s Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

novdocx (en) 24 April 2008

5 Troubleshooting the Identity Assurance Solution 47

5.1 Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

A IAS Installation Security 49

A.1 Identity Assurance Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

A.1.1 Using SSL Connections with Remote Loaders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

A.1.2 Using SSL Connections with JBoss. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

A.2 Novell Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

A.3 Third-Party Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

B Manually Configuring the ActivIdentity Card Management System 51

C Upgrading the Identity Assurance Solution from 3.0.1 to 3.0.2 53

D Documentation Updates 61

D.1 May 12th, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

D.2 March 7th, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

D.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

D.3 February 20, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

D.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6 Identity Assurance Solution 3.0.2 Installation Guide

About This Guide

This guide provides an overview of the Identity Assurance Solution. It includes instructions on how
to install, configure, and manage the solution.

 Chapter 1, “Overview,” on page 9

 Chapter 2, “Planning the Identity Assurance Solution Installation,” on page 17

 Chapter 3, “Installing Identity Assurance Solution,” on page 21

 Chapter 4, “Configuring Identity Assurance Solution,” on page 33

 Chapter 5, “Troubleshooting the Identity Assurance Solution,” on page 47

Audience

This guide is written primarily for network administrators and system integrators.

novdocx (en) 24 April 2008

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 Identity Assurance Solution 3.0.2 Installation Guide, visit the

Identity Assurance Solution Documentation Web site (http://www.novell.com/documentation/
ias301/index.html).

Documentation Conventions

®

In Novell
items in a cross-reference path.

A trademark symbol (
trademark.

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.

documentation, a greater-than symbol (>) is used to separate actions within a step and

®

, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party

About This Guide 7

novdocx (en) 24 April 2008

8 Identity Assurance Solution 3.0.2 Installation Guide

1

Overview

Novell® has partnered with third-party companies to build a solution that offers an integrated logical
and physical control system that complies with Homeland Security Presidential Directive 12
(HSPD-12). HSPD-12 directs the implementation of a new standardized badging process, which is
designed to enhance security, reduce identity fraud, and protect the personal privacy of those issued
government identification.

Identity Assurance Solution (IAS) provides a complete system for managing the enrollment,
issuance, access control, and retirement of Personal Identification Verification (PIV) cards. This
solution is in compliance with the Federal Information Processing Standards Publication 201 (FIPS

201) and provides components such as an Identity Management System (IDMS), a User Enrollment/
Biometric Capture system, a Card Management System (CMS), and Logical and Physical Access
Control Systems (LACS/PACS).

Figure 1-1 shows the different components of the solution and shows how the workflow is designed.

Figure 1-1 Identity Assurance Solution Workflow Overview

novdocx (en) 24 April 2008

1

Overview

9

The components and workflow are discussed in the following sections:

 Section 1.1, “Identity Assurance Solution Components,” on page 10

 Section 1.2, “Driver Overviews,” on page 10

 Section 1.3, “Identity Assurance Solution Workflow,” on page 15

 Section 1.4, “What’s Next,” on page 16

1.1 Identity Assurance Solution Components

Table 1-1 describes the basic components and the specific products in this solution.

Table 1-1 Identity Assurance Solution Components and Products

Component Product

novdocx (en) 24 April 2008

Identity Management System / Identity Vault Novell eDirectory

Novell Identity Manager

Novell iManager

Workflow System User Application for Provisioning

User Enrollment/Biometric Capture system Enrollment Driver for the Honeywell* SmartPlus*

System

Card Management System (CMS) CMS Driver for ActivIdentity* ActivID*

Logical Access Control System (LACS) Novell Enhanced Smart Card Method (NESCM)

Physical Access Control System (PACS) PACS Integration Driver for the Honeywell

SmartPlus System

TM

A more detailed list of components and products is provided in Chapter 2, “Planning the Identity

Assurance Solution Installation,” on page 17.

1.2 Driver Overviews

The IAS drivers provide a means for the different solution components to communicate and work
together. The drivers are a vital part of the IAS solution.

The following sections provide information about each driver:

 Section 1.2.1, “PIV Life Cycle Driver,” on page 11

 Section 1.2.2, “PIV Workflow Driver,” on page 11

 Section 1.2.3, “Enrollment Driver,” on page 11

 Section 1.2.4, “CMS Driver,” on page 12

 Section 1.2.5, “PACS Integration Driver,” on page 14

10 Identity Assurance Solution 3.0.2 Installation Guide

1.2.1 PIV Life Cycle Driver

The PIV Life Cycle driver acts as a traffic director for the solution. It verifies that all expected
attributes are included in each step of the process and either allows the process to continue if all
requirements are met, or halts the process if requirements are not met.

1.2.2 PIV Workflow Driver

The PIV Workflow driver provides a means for the various roles to perform tasks related to
requesting and provisioning PIV cards for users.

1.2.3 Enrollment Driver

The Enrollment driver for the Honeywell SmartPlus system does the following tasks in the PIV
provisioning scenario:

 Creates application user accounts in the Honeywell SmartPlus Enrollment system.

 Provisions sponsor-approved appellation information from the Identity Manager system to the

Honeywell SmartPlus Enrollment system.

 Publishes biometric data and vetting confirmation from the Honeywell SmartPlus Enrollment

system to the Identity Manager system.

novdocx (en) 24 April 2008

 Deletes cardholder biometric data from the Honeywell SmartPlus Enrollment system upon

termination of the user.

The driver contains policies to detect events that indicate when data should be provisioned to or
deprovisioned from the Honeywell SmartPlus Enrollment system. It also contains an event
“listener” capability that allows it to receive data transmissions from the Honeywell SmartPlus
Enrollment system.

In order to maintain a simple interface with Identity Manager, the driver is configured to only
respond to state changes in the fipsBioStatus attribute.

The value of this attribute is modified only by the Enrollment driver or PIV Life Cycle driver. After
the initial provisioning information is added by the sponsor to the user through the PIV Workflow,
the PIV Life Cycle driver sets the fipsBioStatus attribute to a value of Biometric Enrollment Ready.

This modification event triggers the driver to send the account creation and sponsor enrollment data
to the Biometric Enrollment server. If the information is sent and provisioned successfully, the
fipsBioStatus attribute is set to Biometric Enrollment in Progress. If the information fails to be sent
to the server, fipsBioStatus is set to Biometric Enrollment Failure and the fipsBioStatusReason and
fipsBioStatusExplanation attributes contain the reason for the failure.

The PIV Life Cycle driver receives the modify event for the fipsBioStatus attribute and updates the
PIV provisioning state attributes. If the information is submitted successfully to the Honeywell
SmartPlus Enrollment server, the registrar notifies the applicant to report to the biometric enrollment
station, as indicated in Figure 1-2.

Overview 11

Figure 1-2 Enrollment Driver

novdocx (en) 24 April 2008

After the information is entered into the Honeywell SmartPlus Enrollment server, the registrar sends
the completed biometric data package to the driver for storage in the Identity Vault. The driver
stores the biometric data and updates the fipsBioStatus attribute with a value of either Biometric
Enrollment Complete or Biometric Enrollment Failure. The fipsBioStatusReason and
fipsBioStatusExplanation attributes can be updated with relevant success or failure information.

The role of the Enrollment driver is finished at this point in the Identity Assurance Solution.

1.2.4 CMS Driver

The CMS driver for ActivIdentity Active ID is used for the following tasks in the PIV provisioning
scenario:

 Creates applicant user accounts in the Card Management System.

 Sends a Card Production Request (CPR) containing all required data to the Card Management

System.

12 Identity Assurance Solution 3.0.2 Installation Guide

 Notifies Identity Manager of a Card Issued or a Credential Issued event from the Card

Management System.

 Sends card information (card serial number, FIPS 201 required certificate, CHUID) back to

Identity Manager.

 Sends a Card Termination Request to the Card Management System.

The driver contains policies to detect events that indicate when data should be provisioned to or
deprovisioned from the Card Management System.

In order to maintain a simple interface with Identity Manager, the driver is configured to only
respond to state changes in the fipsCMSStatus attribute.

The value of this attribute is modified only by the CMS driver or by the PIV Life Cycle driver. After
the enrollment process is completed successfully, the PIV Life Cycle driver sets the fipsCMSStatus
attribute to a value of PIV Card Production Request Ready and then to CMS User Provisioning
Ready. See Figure 1-3.

Figure 1-3 Card Management System Driver

novdocx (en) 24 April 2008

Overview 13

If the sponsor approves the PIV issuance, the CMS driver sends a User Add request to the Card
Management System. If the User Add request is successful, the fipsCMSStatus attribute is set to
CMS User Provisioning Complete. If the Add request fails, the fipsCMSStatus attribute is set to
CMS User Provisioning Failed and the fipsCMSStatusReason attribute and
fipsCMSStatusExplanation attribute explain why the process failed.

When the CMS User Provisioning is complete, the PIV Life Cycle driver sets the fipsPIVStatus
attribute to CMS User Provisioning Complete and ensures that all attributes for a Card Provisioning
Request (CPR) are present for the user. If so, the PIV Life Cycle driver sets the fipsCMSStatus
attribute and the fipsPIVStatus attribute to PIV Card Production Request Ready.

The CMS driver gathers all available attributes, builds the Card Production Request, and submits it
to the Card Management System. If the sponsor approves the Card Production Request, the PIV Life
Cycle driver sets the fipsCMSStatus attribute and the fipsPIVStatus attribute to PIV Card
Production Approved. The Card Management System driver then sends a production request to the
Card Management System and sets the fipsCMSStatus attribute to PIV Card Issuance Ready.

The CMS driver forwards the results of the card issuance procedure. It sets the fipsCMSStatus
attribute to PIV Card Issued and the fipsCMSPhysicalCardSN attribute to the card’s serial number
value. It also retrieves and stores the card’s certificates from the Card Management System in
Identity Manager.

novdocx (en) 24 April 2008

1.2.5 PACS Integration Driver

The PACS Integration driver for the Honeywell SmartPlus system is used for the following tasks in
the PIV provisioning scenario:

 Creates applicant user accounts in the Physical Access Control system (PACS).

 Sends information to the Honeywell SmartPlus PACS system, stating what locations the user

has access to.

 Deletes the user from the Honeywell SmartPlus PACS system upon termination.

The driver contains policies to detect events that indicate when data should be provisioned to or
deprovisioned from the Honeywell SmartPlus PAC system.

In order to maintain a simple interface with Identity Manager, the driver is configured to only
respond to state changes in the fipsPACSStatus attribute.

The value of this attribute is modified only by the PACS Integration driver or by the PIV Life Cycle
driver. After the PIV card is issued to the applicant, the PIV Life Cycle driver sets the
fipsPACSStatus attribute to a value of PACS Activation Ready. See Figure 1-4.

14 Identity Assurance Solution 3.0.2 Installation Guide

Figure 1-4 Physical Access Control System Driver

novdocx (en) 24 April 2008

This modification event triggers the driver to send the applicant’s PIV card information to the
Honeywell SmartPlus PACS system. If the information is sent and provisioned successfully, the
fipsPACSStatus attributes is set to PACS Activation Ready. If the information fails to be sent to the
system, the fipsPACSStatus is set to PACS Activation Failed and the fipsPACSStatusReason and
fipsPACSStatusExplanation attributes contain the reason for the failure.

The Honeywell SmartPlus PAC system receives the applicant’s information and allows the applicant
physical access to the place of employment.

1.3 Identity Assurance Solution Workflow

Figure 1-1 on page 9 describes the basic workflow of this solution.

1. From a workstation, the sponsor accesses the user application associated with the PIV
Workflow Driver and submits a request for a PIV card for the applicant.

2. The PIV Workflow Driver sends the request to the PIV Life Cycle driver.

3. The PIV Life Cycle driver checks to make sure the request is valid and complete. If it is a valid
request, it routes the request to the Enrollment/Biometric Capture driver.

4. The Enrollment/Biometric Capture driver routes the request to the biometric engine, accessible
by the registrar’s workstation.

5. The applicant meets with the registrar and provides whatever information is required by the
company. The following are examples of information that could be included on the PIV card:

 Signature

 Photo

 Fingerprint

 I9 Form

Overview 15

A background check is also conducted on the applicant.

6. After the enrollment data is captured, the registrar submits it again to the Enrollment/Biometric
Capture driver.

7. The Enrollment/Biometric Capture driver sends the enrollment data to the PIV Life Cycle
driver.

8. The PIV Life Cycle driver checks to make sure the data is valid and complete. If the data is
valid and complete, it routes the request to the Card Management System driver.

9. The Card Management System driver sends a Card Production Request (CPR) to the Card
Management System.

10. The activator creates the PIV card for the applicant.

The applicant meets with the activator to receive the PIV card. The applicant provides a
fingerprint scan to confirm his or her identity and to finalize the PIV card creation and
issuance. When this is successfully completed, the activator hands over the card.

11. After the card is physically issued, the activator sends a Card Issue Event back to the Card
Management System driver. The Card Issue Event contains all the card data.

12. The Card Management System driver notifies the PIV Life Cycle driver of the Card Issue
Event.

13. The PIV Life Cycle driver stores the card data and verifies that everything is in order. If so, the
applicant can now use his or her card for logical access to the network. The PIV Life Cycle
driver notifies the Physical Access Control driver of the card issuance.

14. The Physical Access Control driver sends the information to the Physical Access Control
System. The card is activated for physical access based on the sponsor’s chosen settings.

novdocx (en) 24 April 2008

1.4 What’s Next

 To prepare for the installation, see Chapter 2, “Planning the Identity Assurance Solution

Installation,” on page 17.

 To begin the installation, see Chapter 3, “Installing Identity Assurance Solution,” on page 21.

16 Identity Assurance Solution 3.0.2 Installation Guide

2

Planning the Identity Assurance

novdocx (en) 24 April 2008

Solution Installation

This section describes the minimum requirements that must be met for each machine before starting
the Identity Assurance Solution (IAS) installation. It also describes the contents of each CD
distributed with this solution.

 Section 2.1, “Minimum Requirements,” on page 17

 Section 2.2, “Preparing the Software,” on page 19

 Section 2.3, “Contents of Each Identity Assurance Solution CD,” on page 20

 Section 2.4, “What's Next,” on page 20

2.1 Minimum Requirements

The following minimum requirements apply to this release:

 Section 2.1.1, “Novell Identity Manager Support,” on page 17

 Section 2.1.2, “Identity Vault Server,” on page 18

 Section 2.1.3, “User Enrollment/Biometric Capture Station,” on page 18

 Section 2.1.4, “Card Management System,” on page 18

 Section 2.1.5, “Physical Access Control System,” on page 18

2

 Section 2.1.6, “User Application Server,” on page 18

 Section 2.1.7, “Workstations,” on page 18

 Section 2.1.8, “Web Browser,” on page 19

2.1.1 Novell Identity Manager Support

IAS 3.0.2 supports the following versions of Novell® Identity Manager User Application (a
browser-based Web application that gives the user the ability to perform a variety of identity self­service tasks):

 Identity Manager 3.5.0 with User Application 3.5.0 (http://www.novell.com/documentation/

idm35/pdfdoc/idm350.zip)

 Identity Manager 3.5.1 with User Application 3.6.0 (http://www.novell.com/documentation/

idm35/index.html)

WARNING: IAS 3.0.2 does not support Identity Manager User Application 3.5.1. You must
either upgrade or install Identity Manager User Application 3.6.0. Follow the procedures
outlined in the IDM Migration Guide (http://www.novell.com/documentation/idmrbpm36/

migration/data/seafang_antelope.html).

Planning the Identity Assurance Solution Installation

17

2.1.2 Identity Vault Server

The Identity Vault server must be running Windows* 2003 Server SP1 or later.

2.1.3 User Enrollment/Biometric Capture Station

The software being utilized for the User Enrollment Biometric Capture station for this release is
Honeywell SmartPlus Enrollment software. Make sure this software is installed on the machine you
are designating for this function.

For information on the minimum requirements for the Honeywell SmartPlus Enrollment software,
see the installation documentation provided by Honeywell.

2.1.4 Card Management System

The software being utilized for the Card Management System for this release is the ActivIdentity
CMS 4.0.3 software. Make sure this software is installed on the machine you are designating for this
function.

novdocx (en) 24 April 2008

IMPORTANT: Patch # FISX0709018 is required and must be applied to ActivIdentity CMS 4.0.3.

For information on the minimum requirements for the ActivIdentity CMS software, see the
installation documentation provided by ActivIdentity.

NOTE: For this release, ActivIdentity CMS is only supported on the Windows platform with
Microsoft* Active Directory.*

2.1.5 Physical Access Control System

The software being utilized for the Physical Access Control System for this release is the Honeywell
SmartPlus Integration software. Make sure this software is installed on the machine you are
designating for this function.

For information on the minimum requirements for the Honeywell SmartPlus Integration software,
see the installation documentation provided by Honeywell.

2.1.6 User Application Server

The Identity Vault server must be running Windows 2003 Server SP1 or later.

2.1.7 Workstations

Each workstation must meet the following minimum requirements:

 Windows XP SP2 or later installed.

 PIV card reader is connected and PIV card middleware is installed.

 Use supported PIV cards.

18 Identity Assurance Solution 3.0.2 Installation Guide

 Use supported middleware.

2.1.8 Web Browser

The administration of the Identity Management Solution is supported by using the following
browsers on Windows only:

 Firefox* 1.5.x or later

 Internet Explorer* 6.0 SP2 or later

2.2 Preparing the Software

Identity Assurance Solution is made up of several software components:

 Section 2.2.1, “Novell Products that Need to be Downloaded and Installed,” on page 19

 Section 2.2.2, “Third-Party Products that Need to be Installed,” on page 19

 Section 2.2.3, “IAS CD Images,” on page 19

novdocx (en) 24 April 2008

2.2.1 Novell Products that Need to be Downloaded and Installed

 Novell eDirectoryTM

 Novell Identity Manager

 Novell Audit

2.2.2 Third-Party Products that Need to be Installed

 Honeywell SmartPlus Enrollment

 ActivIdentity CMS

 Honeywell SmartPlus Integration

For more information on installing these products, see Section 3.1, “Installing the User Enrollment

Biometric Capture Station,” on page 21,Section 3.2, “Installing the Card Management System,” on
page 21, and Section 3.3, “Installing the Physical Access Control System,” on page 22.

2.2.3 IAS CD Images

 Configuration files

 Drivers

 Workstation setup software

Download the IAS .iso files and verify the MD 5 values, then create a CD for each .iso file you
downloaded. Label each CD as outlined in the following table:

Filename CD Label

iasmodules_302.iso CD 1-IAS Modules

Planning the Identity Assurance Solution Installation 19