Tivoli Identity Manager

Transcription

1 Tivoli Identity Manager Version 4.6 DB2 Universal Database Adapter Installation and Configuration Guide

2

3 Tivoli Identity Manager Version 4.6 DB2 Universal Database Adapter Installation and Configuration Guide

4 Note: Before using this information and the product it supports, read the information in Appendix D, Notices, on page 65. Seventh Edition (June 2005) This edition applies to version 4.6 of this adapter and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2002, All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Preface v Who should read this book v Publications and related information......v Tivoli Identity Manager library v Prerequisite Product Publications......vii Related Publications viii Accessing publications online viii Accessibility viii Support information ix Conventions used in this book ix Typeface conventions ix Operating system differences x Definitions for HOME and other directory variables x Chapter 1. Overview of the UDB adapter 1 Features of the adapter Chapter 2. Installing and configuring the UDB adapter Prerequisites Testing network connectivity Installing the adapter Importing the adapter profile into the Tivoli Identity Manager Server Importing the adapter profile Creating a UDB service Configuring the adapter Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager Starting the adapter configuration tool Viewing configuration settings Changing protocol configuration settings Configuring event notification Setting event notification triggers Modifying an event notification context Changing the configuration key Changing activity logging settings Changing registry settings Modifying non-encrypted registry settings...21 Modifying encrypted registry settings Changing advanced settings Viewing statistics Accessing help and additional options Chapter 4. Configuring SSL authentication for the UDB adapter.. 29 Overview of SSL and digital certificates Private keys, public keys, and digital certificates 30 Self-signed certificates Certificate and key formats The use of SSL authentication Configuring certificates for SSL authentication...32 Configuring certificates for one-way SSL authentication Configuring certificates for two-way SSL authentication Configuring certificates when the adapter operates as an SSL client Managing SSL certificates using CertTool Starting CertTool Generating a private key and certificate request 37 Installing the certificate Installing the certificate and key from a PKCS12 file Viewing the installed certificate Installing a CA certificate Viewing CA certificates Deleting a CA certificate Viewing registered certificates Registering a certificate Unregistering a certificate Exporting a certificate and key to PKCS12 file..40 Chapter 5. Customizing the UDB adapter Copy the UDBProfile.jar file and extract the files..43 Create a new JAR file and install the new attributes on the Tivoli Identity Manager Server Managing passwords when restoring accounts...44 Chapter 6. Upgrading the UDB adapter or the ADK Upgrading the UDB adapter Upgrading the ADK Log files Chapter 7. Uninstalling the UDB adapter Appendix A. Adapter attributes Attribute descriptions Attributes by UDB Adapter actions Database Login Add Database Login Change Database Login Delete Database Login Suspend Database Login Restore Reconciliation Appendix B. Configuring the UDB adapter for multi-instance support Appendix C. Support information Searching knowledge bases Copyright IBM Corp. 2002, 2005 iii

6 Search the information center on your local system or network Search the Internet Obtaining fixes Contacting IBM Software Support Determine the business impact of your problem 63 Describe your problem and gather background information Submit your problem to IBM Software Support 63 Appendix D. Notices Trademarks Index iv IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

7 Preface Who should read this book The IBM Tivoli Identity Manager DB2 Universal Database Adapter (UDB Adapter) enables connectivity between the Tivoli Identity Manager Server and a network of systems running the UDB RDBMS (Relational Database Management System). After the adapter is installed and configured, Tivoli Identity Manager manages access to UDB RDBMS resources with your site s security system. This book describes how to install and configure the UDB Adapter. Note: The program that is used to connect the managed resource to the Tivoli Identity Manager Server is now called an adapter. The term adapter replaces the previously used term agent. The user interface used to configure the adapter still uses the term agent. This book is intended for UDB RDBMS security administrators responsible for installing software on their site s computer systems. Readers are expected to understand AIX and UDB RDBMS concepts. The person completing the UDB Adapter installation procedure must also be familiar with their site system standards and needs to have appropriate AIX experience and knowledge. Readers should be able to perform routine AIX system and security administration tasks. Publications and related information Read the descriptions of the Tivoli Identity Manager library. To determine which additional publications you might find helpful, read the Prerequisite Product Publications on page vii and the Related Publications on page viii. After you determine the publications you need, refer to the instructions in Accessing publications online on page viii. Tivoli Identity Manager library The publications in the Tivoli Identity Manager technical documentation library are organized into the following categories: v Release information v Online user assistance v Server installation and configuration v Problem determination v Technical supplements v Adapter installation and configuration Release Information: v IBM Tivoli Identity Manager Release Notes Provides software and hardware requirements for Tivoli Identity Manager, and additional fix, patch, and other support information. v IBM Tivoli Identity Manager Documentation Read This First Card Lists the Tivoli Identity Manager publications. Online user assistance: Copyright IBM Corp. 2002, 2005 v

8 Provides online help topics and an information center for all Tivoli Identity Manager administrative tasks. The information center includes information that was previously provided in the IBM Tivoli Identity Manager Configuration Guide and the IBM Tivoli Identity Manager Policy and Organization Administration Guide. Server installation and configuration: IBM Tivoli Identity Manager Server Installation and Configuration Guide for WebSphere Environments provides installation and configuration information for Tivoli Identity Manager. Configuration information that was previously provided in the IBM Tivoli Identity Manager Configuration Guide is now included in either the installation guide or in the IBM Tivoli Identity Manager Information Center. Problem determination: IBM Tivoli Identity Manager Problem Determination Guide provides problem determination, logging, and message information for the Tivoli Identity Manager product. Technical supplements: The following technical supplements are provided by developers or by other groups who are interested in this product: v IBM Tivoli Identity Manager Performance Tuning Guide Provides information needed to tune Tivoli Identity Manager Server for a production environment, available on the Web at: Click the I character in the A-Z product list, and then, click the Tivoli Identity Manager link. Browse the information center for the Technical Supplements section. v Redbooks and white papers are available on the Web at: IBMTivoliIdentityManager.html Browse to the Self Help section, in the Learn category, and click the Redbooks link. v Technotes are available on the Web at: v Field guides are available on the Web at: v For an extended list of other Tivoli Identity Manager resources, search the following IBM developerworks Web address: Adapter installation and configuration: The Tivoli Identity Manager Server technical documentation library also includes an evolving set of platform-specific installation documents for the adapter components of a Tivoli Identity Manager Server implementation. Locate adapters on the Web at: vi IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

9 Passport_Advantage_Home Click Support & downloads. Browse to the Downloads and drivers. Click the link for the current inventory of adapters. Skills and training: The following additional skills and technical training information were available at the time that this manual was published: v Virtual Skills Center for Tivoli Software on the Web at: v Tivoli Education Software Training Roadmaps on the Web at: v Tivoli Technical Exchange on the Web at: supp_tech_exch.html Prerequisite Product Publications To use the information in this book effectively, you must have knowledge of the products that are prerequisites for Tivoli Identity Manager Server. Publications are available from the following locations: v UDB RDBMS v Operating systems IBM AIX Sun Solaris Red Hat Linux Microsoft Windows Server v Database servers IBM DB2 - Support: - Information center: - Documentation: winos2unix/support/v8pubs.d2w/en_main - DB2 product family: - Fix packs: - System requirements: Oracle Preface vii

10 Related Microsoft SQL Server v Directory server applications IBM Directory Server en_us/html/ldapinst.htm Sun ONE Directory Server v WebSphere Application Server Additional information is available in the product directory or Web sites. v WebSphere embedded messaging v IBM HTTP Server Publications Information that is related to Tivoli Identity Manager Server is available in the following publications: v The Tivoli Software Library provides a variety of Tivoli publications such as white papers, datasheets, demonstrations, redbooks, and announcement letters. The Tivoli Software Library is available on the Web at: v The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available from the Glossary link of the Tivoli Software Library Web page at: Accessing publications online IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli software information center Web site. Access the Tivoli software information center at the following Web address: Click the I character in the A-Z list, and then click the Tivoli Identity Manager link to access the product library. Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your paper. Accessibility The product documentation includes the following features to aid accessibility: viii IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

11 v Documentation is available in convertible PDF format to give the maximum opportunity for users to apply screen-reader software. v All images in the documentation are provided with alternative text so that users with vision impairments can understand the contents of the images. Support information If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: v Searching knowledge bases: You can search across a large collection of known problems and workarounds, Technotes, and other information. v Obtaining fixes: You can locate the latest fixes that are already available for your product. v Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with someone from IBM, you can use a variety of ways to contact IBM Software Support. For more information about these ways to resolve problems, see Appendix C, Support information, on page 61. Conventions used in this book Typeface This reference uses several conventions for special terms and actions and for operating system-dependent commands and paths. conventions This guide uses the following typeface conventions: Bold Italic v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text v Words defined in text v Emphasis of words (words as words) v New terms in text (except in a definition list) v Variables and values you must provide Monospace v Examples and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options Preface ix

12 Operating system differences This guide uses the UNIX convention for specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in the Windows operating system is equivalent to $tmp in a UNIX operating system. Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions. Definitions for HOME and other directory variables The following table contains the default definitions that are used in this guide to represent the HOME directory level for various product installation paths. You can customize the installation directory and HOME directory for your specific implementation. If this is the case, you need to make the appropriate substitution for the definition of each variable represented in this table. The value of path varies for these operating systems: v Windows: drive:\program Files v AIX: /usr v Other UNIX: /opt Path Variable Default Definition Description DB_INSTANCE_HOME Windows: path\ibm\sqllib UNIX: v AIX, Linux: /home/dbinstancename v Solaris: /export/home/dbinstancename The directory that contains the database for Tivoli Identity Manager. x IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

13 Path Variable Default Definition Description LDAP_HOME v For IBM Directory Server Version 5.2 The directory that contains the Windows: directory server path\ibm\ldap code. UNIX: AIX, Linux: path/ldap Solaris: path/ibmldaps path/ibm/ldap v For IBM Directory Server Version 6.0 Windows: path\ibm\ldap\v6.0 UNIX: path/ibm/ldap/v6.0 AIX, Solaris Linux: opt/ibm/ldap/v6.0 v For Sun ONE Directory Server Windows: path\sun\mps UNIX: /var/sun/mps IDS_instance_HOME For IBM Directory Server Version 6.0 Windows: drive\ ibmslapd-instance_owner_name The directory that contains the IBM Directory Server Version 6.0 instance. The value of drive might be C:\ on Windows systems. An example of instance_owner_name might be ldapdb2. For example, the log file might be C:\idsslapd-ldapdb2\logs\ibmslapd.log. UNIX: INSTANCE_HOME/idsslapd-instance_name HTTP_HOME On Linux and AIX systems, the default home directory is the /home/instance_owner_name directory. On Solaris systems, for example, the directory is the /export/home/ldapdb2/idsslapdldapdb2 directory. Windows: path\ibmhttpserver UNIX: path/ibmhttpserver The directory that contains the IBM HTTP Server code. Preface xi

14 Path Variable Default Definition Description ITIM_HOME WAS_HOME WAS_MQ_HOME WAS_NDM_HOME Tivoli_Common_Directory Windows: path\ibm\itim UNIX: path/ibm/itim Windows: path\websphere\appserver UNIX: path/websphere/appserver Windows: path\ibm\websphere MQ UNIX: path/mqm Windows: path\websphere\deploymentmanager UNIX: path/websphere/deploymentmanager Windows: path\ibm\tivoli\common\ctgim UNIX: path/ibm/tivoli/common/ctgim The base directory that contains the Tivoli Identity Manager code, configuration, and documentation. The WebSphere Application Server home directory The directory that contains the WebSphere MQ code. The home directory on the deployment manager The central location for all serviceability-related files, such as logs and first-failure capture data xii IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

15 Chapter 1. Overview of the UDB adapter Features of the adapter An adapter is a program that provides an interface between a managed resource and the Tivoli Identity Manager Server. Adapters might or might not reside on the managed resource and the Tivoli Identity Manager Server manages access to the resource by using your security system. Adapters function as trusted virtual administrators on the target platform, performing such tasks as creating login IDs, suspending IDs, and performing other functions administrators normally run manually. The adapter runs as a service, independent of whether or not a user is logged on to the Tivoli Identity Manager Server. The IBM Tivoli Identity Manager UDB Adapter enables connectivity between the Tivoli Identity Manager Server and a system running the UDB RDBMS. This installation guide provides the basic information that you need to install and configure the UDB Adapter. This chapter provides an overview of the adapter and the features of the adapter. You can use the UDB Adapter to automate the following administrative tasks: v Creating new users on the DB2 UDB RDBMS server v Modifying DB2 UDB RDBMS user attributes v Changing the DB2 UDB RDBMS user account password v Suspending, restoring, and deleting DB2 UDB RDBMS user accounts v Looking up user operations for DB2 UDB RDBMS user accounts v Reconciling DB2 UDB RDBMS user accounts Copyright IBM Corp. 2002,

16 2 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

17 Chapter 2. Installing and configuring the UDB adapter Installing and configuring the UDB Adapter involves several steps that you must complete in the appropriate sequence. Review the prerequisites before you begin the installation process. You can also create an account on the managed resource for the adapter to use. Prerequisites Table 1 identifies hardware, software, and authorization prerequisites to install the UDB Adapter. Verify that all of the prerequisites have been met before installing the UDB Adapter. Table 1. Prerequisites for installing the UDB adapter System v A 32 bit x86 based microprocessor. v A minimum of 256 MB of memory. v A minimum of 300 MB of free disk space. Operating System One of the following versions of AIX must be installed and operational on the system where the adapter is installed: v 5.1 v 5.2 DB2 Database v DB2 UDB 7.1 RDBMS v DB2 UDB 7.2 RDBMS Note: The DB2 UDB RDBMS does not have to be on the same system as the adapter. DB2 Client Software The following versions of the DB2 client must be installed on the system where the adapter will run: v DB2 UDB 7.1 v DB2 UDB 7.2 These two versions of the client can connect to either DB2 UDB 7.1 RDBMS or DB2 UDB 7.2 RDBMS. Network Connectivity TCP/IP network System Administrator The person completing the UDB Adapter installation Authority procedure must have system administrator authority to complete the steps in this chapter. For every database that the adapter manages, you must provide an operating system account with SYSADM authority on the DB2 UDB RDBMS. Tivoli Identity Manager Server Version 4.6 Testing network connectivity To test network connectivity and file transfer capability between the AIX workstation where the UDB Adapter will be installed and the workstation where the Tivoli Identity Manager Server is installed, complete these steps. 1. Log on to the AIX workstation as root or superuser. Copyright IBM Corp. 2002,

18 Installing the adapter 2. Test communication between the system where the Tivoli Identity Manager Server is located and the AIX workstation. # ping AIX_host_name The Tivoli Identity Manager UDB Adapter installation files are available for download from the IBM Web site. Contact your IBM account representative for the Web address and download instructions. In order to install the adapter, complete the following steps: 1. Download the UDB Adapter compressed installation file from the Web site. 2. Extract the contents of the compressed file into a temporary directory and navigate to that directory. 3. Type./setupaix.bin and press Enter to run the installation program. 4. On the Welcome window, click Next. 5. On the License Agreement window, review the license agreement and decide if you accept the terms of the license. If you do, select Accept and click Next. 6. Type the account name for the account used to manage the DB2 UDB database, and click Next. 7. On the Select Destination Directory window, specify where you want to install the adapter in the Directory Name field. You can accept the default location, or click Browse to specify a different directory. Then, click Next. Installer Click Next to install < agentname> to this directory, or click Browse to install to a different directory. Directory Name: /home/tivoli/< agentname> Browse... InstallShield < Back Next > Cancel Figure 1. Select Destination Directory window 8. On the Installation Summary window, click Next to begin the installation. 9. On the Installation Completed window, click Finish to exit the program. 4 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

19 The UDB Adapter can manage multiple database instances at the same time. For more information on managing multiple database instances, see Appendix B, Configuring the UDB adapter for multi-instance support, on page 59. Importing the adapter profile into the Tivoli Identity Manager Server Before you can add an adapter as a service to the Tivoli Identity Manager Server, the server must have an adapter profile to recognize the adapter as a service. The files that are packaged with the UDB Adapter include the adapter JAR file, UDBProfile.jar. Using the Import feature of the Tivoli Identity Manager Server, you can import the adapter profile into the server as a service profile. The UDBProfile.jar file includes all of the files that are needed to define the adapter schema, account form, service form and profile properties. Importing the adapter profile An adapter profile defines the types of resources that the Tivoli Identity Manager Server can manage. You must import the adapter profile into the Tivoli Identity Manager Server before using the UDB Adapter. The profile is used to create a UDB Adapter service on the Tivoli Identity Manager Server and to communicate with the adapter. Before you begin to import the adapter profile, verify that the following conditions are met: v The Tivoli Identity Manager Server must be installed and running. v You must have root or Administrator authority on the Tivoli Identity Manager Server. In order to import the adapter profile, complete the following steps: 1. Log into the Tivoli Identity Manager Server using an account that has the authority to perform administrative tasks. 2. On the Main Menu Navigation Bar, select the Configuration tab. 3. On the Configuration window, select Import/Export Import tabs. 4. On the Import window, in the File to Upload field, type the location of the UDBProfile.jar file, or click Browse to locate the file. 5. Click the Import data into Identity Manager link to import the adapter profile into the Tivoli Identity Manager Server. v If the adapter profile is imported successfully, the following message is displayed: Profile installation complete. v If the adapter profile is not imported successfully, the following message is displayed: Profile installation failed. When you import the adapter profile, if you receive an error related to the schema, the trace.log file will contain information about that error. The trace.log file location is specified by the handler.file.filedir property that is defined in the Tivoli Identity Manager enrolelogging.properties file, which is located in the Tivoli Identity Manager \data directory. Chapter 2. Installing and configuring the UDB adapter 5

20 Creating a UDB service After the adapter profile is imported into the Tivoli Identity Manager Server, you must create a provisioning service to allow Tivoli Identity Manager to communicate with the adapter. In order to create a provisioning service, complete the following steps: 1. Log in to the Tivoli Identity Manager Server using an account that has the authority to perform administrative tasks. 2. On the Main Menu Navigation Bar, click the Provisioning tab. 3. On the Provisioning window, click the Manage Services tab. 4. On the Manage Services window, click Add. 5. From the list of service types, select UDB Profile, and then click Continue. The UDB Adapter service form is displayed. The service form contains the following fields: Service UDB Name Specify a name that defines this UDB service on the Tivoli Identity Manager Server. Service Name is a required field. Service The name of the UDB instance to which the adapter connects. Description Specify an optional description for this service. URL Specify the location and port number of the UDB Adapter. URL is a required field. User Configuring the adapter If https is specified as part of the URL, the adapter must be configured to use SSL authentication. If the adapter is not configured to use SSL authentication, specify http for the URL. For additional information about configuring the adapter to use SSL authentication, see Chapter 4, Configuring SSL authentication for the UDB adapter, on page 29. ID Specify a Directory Access Markup Language (DAML) protocol user name. User ID is a required field. Password Specify the password for the DAML protocol user name. Password is a required field. Owner Specify the service owner, if any. Owner is an optional field. Service Prerequisite Specify an existing Tivoli Identity Manager service that is a prerequisite for the UDB service. 6. To verify the connection, press Test. 7. To create the service, press Submit. Once you have installed the Tivoli Identity Manager UDB Adapter and imported the adapter profile, configuration is required to ensure that it functions properly. In order to configure the UDB Adapter, complete the following steps: 6 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

21 1. Start the UDB Adapter service from the /bin directory of the adapter with./startagent.sh. 2. Configure DAML to ensure communication with the Tivoli Identity Manager Server. For more information on configuring DAML, see Changing protocol configuration settings on page Configure the UDB Adapter to communicate with the Tivoli Identity Manager Server by configuring the adapter for event notification. For more information on configuring event notification, see Configuring event notification on page For secure communication, install a certificate on the machine where the adapter resides and on the Tivoli Identity Manager Server. For more information on installing certificates, see Chapter 4, Configuring SSL authentication for the UDB adapter, on page Use the agentcfg utility to modify the adapter parameters. For more information on parameter configuration, see Chapter 3, Configuring the UDB adapter for IBM Tivoli Identity Manager, on page Define the Service Names for the UDB Adapter to manage. 7. Add and then configure the service form on the Tivoli Identity Manager Server. For more information about adding and configuring a service form, see Creating a UDB service on page Configure the adapter account form. For more information on configuring the adapter account form, refer to the IBM Tivoli Identity Manager Information Center. Chapter 2. Installing and configuring the UDB adapter 7

22 8 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

23 Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager This chapter describes how to use agentcfg, the provided adapter configuration program, to view or modify UDB Adapter parameters. All modifications made to settings with this tool take effect immediately. Starting the adapter configuration tool In order to start the adapter configuration tool, agentcfg, for UDB Adapter parameters, complete these steps: 1. Log into the UDB Adapter system. 2. In the command prompt window, change to the bin directory for the adapter. For example, type the following command, if the UDB Adapter directory is in the default location: (Assume a user called usr has /usr/tivoli as the home directory.) # cd usr/tivoli/agents/udbagent/bin 3. Type the following command: agentcfg -agent UDBAgent You can also use agentcfg to view or change configuration settings from a remote computer. See the table in Accessing help and additional options on page 25 for procedures on using additional arguments. 4. At the Enter configuration key for Agent UDBAgent : prompt, type the configuration key for the UDB Adapter. The default configuration key is agent. You must change the configuration key once installation completes, to prevent unauthorized access to the configuration of the adapter. See Changing protocol configuration settings on page 10 for procedures to change the configuration key. The Main Configuration menu is displayed. UDBAgent 4.6 Agent Main Configuration Menu A. Configuration Settings. B. Protocol Configuration. C. Event Notification. D. Change Configuration Key. E. Activity Logging. F. Registry Settings. G. Advanced Settings. H. Statistics. I. Codepage Support. X. Done Select menu option: From the Main Menu, you can configure the protocol, view statistics, and modify settings, including configuration, registry, and advanced settings. Table 2. Options for the main configuration menu Option Configuration task For more information A Viewing configuration settings See page 10. Copyright IBM Corp. 2002,

24 Table 2. Options for the main configuration menu (continued) Option Configuration task For more information B Changing protocol configuration settings See page 10. C Configuring event notification See page 13. D Changing the configuration key See page 19. E Changing activity logging settings See page 19. F Changing registry settings See page 21. G Changing advanced settings See page 24. H Viewing statistics See page 25. Viewing configuration settings The following procedure describes how to view the UDB Adapter configuration settings. 1. At the Agent Main Configuration Menu, type A. The configuration settings for the UDB Adapter are displayed. The following screen is an example of the UDB Adapter configuration settings. Configuration Settings Name : UDBAgent Version : 4.6 ADK Version : 4.64 ERM Version : 4.64 License : NONE Asynchronous ADD Requests : TRUE (Max.Threads:3) Asynchronous MOD Requests : TRUE (Max.Threads:3) Asynchronous DEL Requests : TRUE (Max.Threads:3) Asynchronous SEA Requests : TRUE (Max.Threads:3) Available Protocols : DAML Configured Protocols : DAML Logging Enabled : TRUE Logging Directory : /usr/tivoli/agents/udbagent/log Log File Name : UDBAgent.log Max. log files : 3 Max.log file size (Mbytes) : 1 Debug Logging Enabled : TRUE Detail Logging Enabled : FALSE Press any key to continue 2. Press any key to return to the Main Menu. Changing protocol configuration settings The UDB Adapter uses the DAML protocol to communicate with the Tivoli Identity Manager Server. By default, when the adapter is installed, the DAML protocol is configured to be used in nonsecure mode. In order to configure a secure environment, you must configure the DAML protocol to use SSL and install a certificate. Refer to Installing the certificate on page 38 for more information about installing certificates. In previous versions of this adapter, you could add and remove protocols. However, in the latest version of this adapter, the DAML protocol is the only supported protocol that you can use. Therefore, you will not need to add or remove a protocol. 10 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

25 In order to configure the DAML protocol for the UDB Adapter, complete the following steps: 1. At the Agent Main Configuration Menu, type B. The DAML protocol is configured and available by default for the UDB Adapter. Agent Protocol Configuration Menu Available Protocols: DAML Configured Protocols: DAML A. Add Protocol. B. Remove Protocol. C. Configure Protocol. X. Done Select menu option 2. At the Agent Protocol Configuration Menu, type C. The Configure Protocol menu is displayed. 3. At the Configure Protocol menu, type C. The Protocol Properties menu for the configured protocol is displayed with protocol properties. The properties on your menu might be different from the ones shown in the examples. The following screen is an example of the DAML protocol properties: DAML Protocol Properties A. USERNAME ****** ;Authorized user name. B. PASSWORD ****** ;Authorized user password. C. MAX_CONNECTIONS 100 ;Max Connections. D. PORTNUMBER ;Protocol Server port number. E. USE_SSL FALSE ;Use SSL secure connection. F. SRV_NODENAME ;Event Notif. Server name. G. SRV_PORTNUMBER 9443 ;Event Notif. Server port number. H. VALIDATE_CLIENT_CE FALSE ;Require client certificate. I. REQUIRE_CERT_REG FALSE ;Require registered certificate. X. Done Select menu option: 4. Type the letter of the menu option for the protocol property that you want to configure. See Table 3 below for additional information about the properties that you can configure for the DAML protocol. Table 3. Options for the DAML protocol menu Option Configuration task A The following prompt is displayed: Modify Property USERNAME : Type a user ID, for example, admin. This value is the user ID that the Tivoli Identity Manager Server uses to connect to the adapter. B The following prompt is displayed: Modify Property PASSWORD : Type a password, for example, admin. This value is the password for the user ID that the Tivoli Identity Manager Server uses to connect to the adapter. Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 11

26 Table 3. Options for the DAML protocol menu (continued) Option Configuration task C The following prompt is displayed: Modify Property MAX_CONNECTIONS : Enter the maximum number of concurrent open connections that the adapter supports. The default number is 100. D The following prompt is displayed: Modify Property PORTNUMBER : Type a different port number. This value is the port number that the Tivoli Identity Manager Server uses to connect to the adapter. The default port number is E The following prompt is displayed: Modify Property USE_SSL : Enter TRUE or FALSE to specify whether a secure SSL connection will be used to connect to or from the adapter. The default value is FALSE. You must install a certificate when USE_SSL is set to TRUE. For more information on certificate installation, see Installing the certificate on page 38. F The following prompt is displayed: Modify Property SRV_NODENAME : Type a server name or an IP address, for example, This value is the DNS name or IP address of the Tivoli Identity Manager Server that is used for event notification and asynchronous request processing. Note: If your platform supports Internet Protocol version 6 (IPv6) connections, you can specify an IPv6 server. G The following prompt is displayed: Modify Property SRV_PORTNUMBER : Type a different port number to access the Tivoli Identity Manager Server. This value is the port number that the adapter uses to connect to the Tivoli Identity Manager Server. The default port number is IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

27 Table 3. Options for the DAML protocol menu (continued) Option Configuration task H The following prompt is displayed: Modify Property VALIDATE_CLIENT_CE : Type TRUE to require the Tivoli Identity Manager Server to send a certificate when it communicates with the adapter. Type FALSE to allow the Tivoli Identity Manager Server to communicate with the adapter without a certificate. The default value is FALSE. Notes: 1. If you set this option to TRUE, you must configure options D through H. 2. The property name is actually VALIDATE_CLIENT_CERT. It is truncated by agentcfg to fit onto the screen. 3. You must use CertTool to install the appropriate CA certificates and optionally register the Tivoli Identity Manager Server certificate. For more information on using CertTool, see Managing SSL certificates using CertTool on page 35. I The following prompt is displayed: Modify Property REQUIRE_CERT_REG : This value only applies when option H is set to TRUE. Type TRUE to require the client certificate from the Tivoli Identity Manager Server to be registered with the adapter before it will accept an SSL connection. Type FALSE to require the client certificate only be verified against the list of CA certificates. The default value is FALSE. For more information on certificates, see Chapter 4, Configuring SSL authentication for the UDB adapter, on page 29. Configuring event notification 5. At the prompt, change the value, and press Enter. The Protocol Properties menu is displayed with your new settings. If you do not want to change the value, just press Enter to return to the Protocol Properties menu. 6. Repeat steps 4 and 5 to configure as many protocol properties as you need to. 7. At the Protocol Properties menu, type X to exit the menu. Event notification is a feature of the UDB Adapter that updates the Tivoli Identity Manager Server at set intervals. Event notification detects changes that are made on the managed resource and updates the Tivoli Identity Manager Server with the changes. You can enable event notification if you want to have updated information from the managed resource sent back to the Tivoli Identity Manager Server between full reconciliations. Event notification is not intended to replace reconciliations on the Tivoli Identity Manager Server. When event notification is enabled, a database of the reconciliation data is kept on the machine where the adapter is installed. The database is updated with the changes that are requested by the Tivoli Identity Manager Server and will stay in synchronization with the server. You can specify an interval for the event Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 13

28 notification process to compare the database to data that currently exists on the managed resource. When the interval has elapsed, any differences between the managed resource and the database are forwarded to the Tivoli Identity Manager Server and updated in the local snapshot database. There are several steps to enabling event notification. These steps assume that the adapter is communicating successfully with the managed resource and the Tivoli Identity Manager Server. First, you must configure the host name, port number, and login information for the Tivoli Identity Manager Server. In order to identify the server for the DAML protocol to use, complete the following steps: 1. At the Agent Protocol Configuration Menu, select Configure Protocol. For more information on configuring a protocol, see Changing protocol configuration settings on page Type the menu option for the SRV_NODENAME property. 3. Specify the IP address or server name that identifies the Tivoli Identity Manager Server, and press Enter. The Protocol Properties menu is displayed with your new settings. 4. Type the menu option for the SRV_PORTNUMBER property. 5. Specify the port number that the adapter uses to connect to the Tivoli Identity Manager Server for event notification band press Enter. The Protocol Properties menu is displayed with your new settings. The example menu shows all of the options displayed when Event Notification is enabled. If Event Notification is disabled, not all of the options are displayed. In order to set Event Notification for the Tivoli Identity Manager Server, complete the following steps: 1. At the Agent Main Configuration Menu, type C. The Event Notification Menu is displayed. Event Notification Menu * Reconciliation interval : 1 day(s) * Next Reconciliation time : 23 hour(s) 56 min(s). 23 sec(s). * Configured Contexts : Jupiter, dd309 A. Enabled B. Time interval between reconciliations. C. Set Processing cache size. (currently: 50 Mbytes) D. Start event notification now. E. Set attributes to be reconciled. F. Reconciliation process priority. (current: 1) G. Add Event Notification Context. H. Modify Event Notification Context. I. Remove Event Notification Context. J. List Event Notification Contexts. X. Done Select menu option: Note: This menu shows all of the options that are displayed when Event Notification is enabled. If Event Notification is disabled, all of the options will not be displayed. 2. Type the menu option of the letter that you want to change. Option A must be enabled in order for the values of the other options to take effect. 14 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

29 Press Enter to return to the Agent Event Notification menu without changing the value. Table 4. Options for the event notification menu Option Configuration task A If this option is enabled, the adapter updates the Tivoli Identity Manager Server with changes to the adapter at regular intervals. Type A to toggle between the options. When the option is set to: v Disabled, it automatically changes to enabled v Enabled, it automatically changes to disabled B The following prompt is displayed: Enter new interval ([ww:dd:hh:mm:ss]) Type a different reconciliation interval. For example: [00:01:00:00:00] Note: This value is the interval to wait once event notification completes before it is run again. The event notification process is resource intensive, therefore this value must not be set to run too frequently. C The following prompt is displayed: Enter new cache size[5]: Type a different value to change the processing cache size. D If this option is selected, event notification is started. E The Event Notification Entry Types menu is displayed. See Setting event notification triggers on page 16 for more information. F The following prompt is displayed: Enter new thread priority [1-10]: Type a different thread value to change the event notification process priority. Setting the thread priority to a lower value reduces the impact that the event notification process has on the performance of the adapter. A lower value might also cause event notification to take longer. G The following prompt is displayed: Context name: Type the new context name, and press Enter. The new context is added. H A menu listing the available contexts is displayed. See Modifying an event notification context on page 17 for more information. I The Remove Context menu is displayed. Select the context to remove. The following prompt is then displayed: Delete context context1? [no]: Press Enter to exit without deleting the context, or type Yes and press Enter to delete the context. Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 15

30 Table 4. Options for the event notification menu (continued) Option Configuration task J The Event Notification Contexts are displayed in the following format: Context Name : Context1 Target DN : erservicename=context1,o=ibm, ou=ibm,dc=com --- Attributes for search request --- {search attributes listed} If you changed the value for options B, C, E, or F, press Enter. The other options are automatically changed when you type the corresponding menu option letter. The Event Notification menu is displayed with your new settings. Setting event notification triggers By default, all attributes are queried for value changes. Attributes that change frequently (for example, password age or last successful logon) must be omitted. 1. At the Event Notification Menu, type E. The Event Notification Entry Types menu is displayed. Event Notification Entry Types A. USER B. GROUP X. Done Select menu option: The USER and GROUP types will not appear in the above menu until the following conditions have been met: a. Event notification has been enabled b. A context has been created and configured c. A full reconciliation has been run 2. Type A for a list of the attributes returned during a user reconciliation, or type B for attributes returned during a group reconciliation. The Event Notification Attribute Listing for the selected reconciliation type is displayed. The default setting lists all attributes that the adapter supports. The example below lists example attributes, and might differ from the list that is displayed on your machine. Event Notification Attribute Listing (a) **erudbinstancename (b) **erudbprivindextab (c) **erudbprivselectview (d) **erudbindexname (e) **eruid (f) **erudbprivupdatetab (g) **erudbprivaltertab (h) **erudbprivinserttab (i) **erudbprivupdateview (j) **erudbprivwgrtabalter (k) **erudbprivinsertview (l) **erdepartment (m) **erudbprivdatabase (n) **erudbprivreftab (o) **erudbprivusetabspace (p) **erprivdeleteview (q) **erudbprivselecttab (r) **eraccountstatus (p)rev page 1 of 3 (n)ext X. Done Select menu option: 3. Type the letter option for the attribute to exclude from an event notification. 16 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

31 Attributes that are marked with the asterisks are returned during the event notification. Attributes that are not marked with asterisks are not returned during the event notification. Modifying an event notification context An event notification context corresponds to a service on the Tivoli Identity Manager Server. Some adapters support multiple services. One UDB Adapter can have several Tivoli Identity Manager services, by specifying a different base point for each service. The base point for the UDB Adapter is the point in the directory server that is used as the root for the adapter. This base point can be an organizational unit (OU) or domain container (DC) base point. Because the base point is an optional value, if a value is not specified, the adapter uses the default domain of the machine on which it is installed. You can have multiple event notification contexts, but you must have at least one adapter. In the example screen below, note that Context1, Context2, and Context3 are three different contexts, all having a different base point. In order to modify an event notification context, complete the following steps: 1. At the Event Notification menu, type H. The Modify Context Menu is displayed. Modify Context Menu A. Context1 B. Context2 C. Context3 X. Done Select menu option: 2. Type the letter of the menu option for the context that you want to modify. The Modify Context menu for the selected context is displayed. A. Set attributes for search B. Target DN: C. Delete Baseline Database X. Done Select menu option: Table 5. Options for the modify context menu Option Configuration task For more information A Adding search attributes for event notification See page 17. B Configuring the target DN for event notification contexts C Removing the baseline database for event notification contexts See page 18. See page 19. Adding search attributes for event notification For some adapters, you might need to specify an attribute-value pair for one or more contexts. These attribute-value pairs, which are defined by completing the steps below, serve multiple purposes: v When multiple services are supported by a single adapter, each service needs to specify one or more attributes to differentiate it from the other services. Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 17

32 v The search attributes are passed to the event notification process, once the event notification interval has occurred or is started manually. For each context, a full search request is sent to the adapter. Additionally, the attributes specified for that context are passed to the adapter. v When the Tivoli Identity Manager Server initiates a reconciliation process, the adapter replaces the local database that represents this service with the new database. In order to add search attributes, complete the following steps: 1. At the Modify Context menu for the context, type A. The Reconciliation Attribute Passed to Agent menu is displayed. Reconciliation Attributes Passed to Agent for Context: Context A. Add new attribute B. Modify attribute value C. Remove attribute X. Done Select menu option: The UDB Adapter requires the erudbinstancename attribute to be specified for each context. This is the name of the instance that the adapter connects to. The value of the attribute must be set to the Service Name defined on the Tivoli Identity Manager Service Form. 2. Type the letter of the menu option of the letter that you want to change. The supported attribute names will be displayed with two asterisks (**) in front of each name. When you type the letter of an attribute, it will toggle the asterisks on and off. Attributes without asterisks will not be updated during an event notification. The Reconciliation Attributes Passed to Agent menu is displayed with the changes displayed. Configuring the target DN for event notification contexts The target DN field holds the unique name of the service that receives event notification updates. In order to configure the target DN, complete the following steps: 1. At the Modify Context menu for the context, type B. The following prompt is displayed: Enter Target DN: 2. Type the target DN for the context, and press Enter. The target DN for the event notification context must be in the following format: erservicename=erservicename,o=organizationname,ou=tenantname,rootsuffix Each element of the DN is defined as follows: erservicename Name of the target service. o Name of the organization. ou Name of the tenant in which the organization is located. rootsuffix Root of the directory tree. The Modify Context menu is displayed with the new target DN listed. 18 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

33 Removing the baseline database for event notification contexts This option is only available once a context is created and a reconciliation is run on the context to create a Baseline Database file. At the Modify Context menu for the context, type C. The Modify Context menu is displayed with the Delete Baseline Database option removed. Changing the configuration key You use the configuration key as a password to access the configuration tool for the adapter. In order to change the UDB Adapter configuration key, complete the following steps: 1. At the Main Menu prompt, type D. 2. Change the value of the configuration key, and press Enter. Press Enter to return to the Main Configuration menu without changing the configuration key. The default configuration key is agent. Make sure that you choose passwords that cannot be easily guessed. The following message is displayed: Configuration key successfully changed. Changing activity logging settings The configuration program exits, and the Main Menu prompt is displayed. When you enable logging, Tivoli Identity Manager maintains a dated log file of all transactions, UDBAgent.log. By default, the log file is located in the /log directory. In order to change the UDB Adapter activity logging settings, complete the following steps: 1. At the Main Menu prompt, type E. The Agent Activity Logging menu is displayed. The following example shows the default activity logging settings. Agent Activity Logging Menu A. Activity Logging (Enabled). B. Logging Directory (current: /usr/tivoli/agents/udbagent/log). C. Activity Log File Name (current: UDBAgent.log). D. Activity Logging Max. File Size ( 1 mbytes) E. Activity Logging Max. Files ( 3 ) F. Debug Logging (Enabled). G. Detail Logging (Disabled). H. Base Logging (Disabled). I. Thread Logging (Disabled). X. Done Select menu option: 2. Type the menu option letter of the activity logging option that you want to change. Option A must be enabled in order for the values of the other options to take effect. Press Enter to return to the Agent Activity Logging menu without changing the value. Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 19

34 Table 6. Options for the activity logging menu Option Configuration task A Set this option to Enabled to have the adapter maintain a dated log file of all transactions. Type A to toggle between the options. When the option is set to: v Disabled, typing an A automatically changes the option to Enabled v Enabled, typing an A automatically changes the option to Disabled B The following prompt is displayed: Enter log file directory: Type a different value for the logging directory, for example, /home/log. When the logging option is enabled, details about each access request are stored in the logging file that is located in this directory. C The following prompt is displayed: Enter log file name: Type a different value for the log file name. When the logging option is enabled, details about each access request are stored in the logging file. D The following prompt is displayed: Enter maximum size of log files (mbytes): Type a new value, for example, 10. The oldest data is archived when the log file reaches the maximum file size. File size is measured in megabytes. It is possible for the activity log file size to exceed disk capacity. E The following prompt is displayed: Enter maximum number of log files to retain: Type a new value up to 100, for example, 5. The adapter automatically deletes the oldest activity logs beyond the specified limit. F If this option is set to enabled, the adapter includes the debug statements in the log file of all transactions. Type F to toggle between the options. When the option is set to: v Disabled, typing an F automatically changes the option to Enabled v Enabled, typing an F automatically changes the option to Disabled G If this option is set to enabled, the adapter maintains a detailed log file of all transactions. The detail logging option must be used for diagnostic purposes only. Detailed logging enables more messages from the adapter and might increase the size of the logs. Type G to toggle between the options. When the option is set to: v Disabled, typing an G automatically changes the option to Enabled v Enabled, typing an G automatically changes the option to Disabled H If this option is set to enabled, the adapter maintains a log file of all transactions in the Agent Development Kit (ADK) and library files. Base logging will substantially increase the size of the logs. Type H to toggle between the options. When the option is set to: v Disabled, typing an H automatically changes the option to Enabled v Enabled, typing an H automatically changes the option to Disabled 20 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

35 Table 6. Options for the activity logging menu (continued) Option Configuration task I If this option is enabled, the log file will contain thread IDs, in addition to a date and timestamp on every line of the file. Type I to toggle between the options. When the option is set to: v Disabled, typing an H automatically changes the option to Enabled v Enabled, typing an H automatically changes the option to Disabled Changing registry settings 3. Press Enter if you changed the value for option B, C, D, or E. The other options are changed automatically when you type the corresponding menu option letter. The Agent Activity Logging menu is displayed with your new settings. The following procedure describes how to change the UDB Adapter registry settings. 1. At the Main Menu, type F. The Registry Settings Menu is displayed. UDBAgent 4.6 Agent Registry Menu A. Modify Non-encrypted registry settings. B. Modify encrypted registry settings. C. Multi-instance settings. X. Done Select menu option: 2. See the following procedures on modifying registry settings. Note: For every UDB database that the UDB Adapter manages, you must define the non-encrypted and encrypted registry items. The registry item for the non-encrypted registry settings is the user name of the administrative user of the UDB Service. The registry item for the encrypted registry settings is the password of the administrative user of the UDB Service. The format of these registry items is explained in Modifying non-encrypted registry settings and Modifying encrypted registry settings on page 23. Modifying non-encrypted registry settings In order to modify the non-encrypted registry settings, complete the following steps: 1. At the Agent Registry Menu, type A. The Non-encrypted Registry Settings Menu is displayed. Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 21

36 Agent Registry Items ENROLE_Version Data_Dir /usr/tivoli/agents/udbagent/data/ 03. UDBAdkDb_File UDBAdkDb 04. UDBServicesample db2inst Page 1 of 1 A. Add new attribute B. Modify attribute value C. Remove attribute X. Done Select menu option: 2. Type the menu letter for the action that you want to perform on an attribute. Table 7. Attribute configuration option descriptions Option Configuration task A Add new attribute B Modify attribute value C Remove attribute 3. Type the registry item name, and press Enter. See Table 8 for a description of each registry key. 4. If you selected option A or B, type the registry item value and press Enter. The Non-encrypted Registry Settings Menu displays the new settings. Note: The key for the administrative user of the UDB Service must be in the following format: UDBService <alias-name> where alias-name is the alias of the cataloged database to which the adapter will connect. The alias-name is the same as the UDB Service that was given in the profile service form, as explained in Creating a UDB service on page 6. The value for this key should be the administrative user of the cataloged database. For example, for the UDB alias sample with username db2inst1, you must enter: v Registry Item Name: UDBServicesample v Registry Item Value: db2inst1 Table 8 describes the non-encrypted registry keys and their available settings: Table 8. Non-encrypted registry key descriptions Key Description Data_Dir Specifies the path of the data directory UDBAdkDB_File Specifies the file name of AdkDB, which contains the login ID of the user and the ConnectString for DB2 UDB RDBMS. ConnectString is used to connect to DB2 and to locate the user in DB2. UDBService<alias-name> Specifies the administrative user of the cataloged database, where <alias-name> is the alias of the cataloged database to which the adapter connects. 22 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

37 Modifying encrypted registry settings In order to modify the encrypted registry settings, complete the following steps: 1. At the Agent Registry Menu, type B. The Encrypted Registry Settings Menu is displayed. Encrypted Registry Items UDBPasswdsample ***** Page 1 of 1 A. Add new attribute. B. Modify attribute value. C. Remove attribute. X. Done Select menu option: 2. Type the menu letter for the action that you want to perform on an attribute. Table 9. Attribute configuration option descriptions Option Configuration task A Add new attribute B Modify attribute value C Remove attribute 3. Type the registry item name, and press Enter. 4. If you selected option A or B, type the registry item value and press Enter. The Encrypted Registry Settings Menu displays the new settings. Note: The key for the password of the administrative user of the UDB Service must be in the following format: UDBPasswd <alias-name> where alias-name is the alias of the cataloged database to which the adapter will connect. The alias-name is the same as the UDB Service that was given in the profile service form, as explained in Creating a UDB service on page 6. The value for this key should be the password of the administrative user of the cataloged database. For example, for the UDB alias sample with the administrative user password db2inst1, you must enter: v Registry Item Name: UDBPasswdsample v New Registry Item Value: v Verification: Table 10 describes the encrypted registry keys and their available settings: Table 10. Encrypted registry key descriptions Key Description UDBPasswd<alias-name> Specifies the password of the administrative user of the cataloged database, where <alias-name> is the alias of the cataloged database to which the adapter connects. Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 23

38 Changing advanced settings You can change the UDB Adapter thread count settings for the following types of requests: v System Login Add v System Login Change v System Login Delete v Reconciliation These settings determine the maximum number of requests that the UDB Adapter processes concurrently. In order to change these settings, complete the following steps: 1. At the Main Menu prompt, type G. The Advanced Settings menu is displayed. The following example shows the default thread count settings. UDBAgent 4.6 Advanced Settings Menu A. Single Thread Agent (current:true) B. ADD max. thread count. (current:3) C. MODIFY max. thread count. (current:3) D. DELETE max. thread count. (current:3) E. SEARCH max. thread count. (current:3) F. Allow User EXEC procedures (current:false) G. Archive Request Packets (current:false) H. UTF8 Conversion support (current:true) I. Pass search filter to agent (current:false) J. Thread Priority Level (1-10) (current:4) X. Done Select menu option: 2. Type the menu option letter of the advanced setting that you want to change. For a description of each option, see Table 11 describes the advanced settings. Table 11. Options for the advanced settings menu Option Description A Forces the adapter to allow only one request at a time. The default value is TRUE. B Controls how many simultaneous ADD requests can run at one time. The default value is 3. C Controls how many simultaneous MODIFY requests can run at one time. The default value is 3. D Controls how many simultaneous DELETE requests can run at one time. The default value is 3. E Controls how many simultaneous SEARCH requests can run at one time. The default value is 3. F Determines whether the adapter allows pre- and post-exec functions. Enabling this option is a potential security risk. The default value is FALSE. G This option is no longer supported. 24 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

39 Table 11. Options for the advanced settings menu (continued) Option Description H This option is no longer supported. I Currently, this adapter does not support processing filters directly. This option must always be FALSE. J Sets the thread priority level for the adapter. The default value is Change the value, and press Enter. The Advanced Settings menu is displayed with your new settings. Viewing statistics In order to view an event log for the UDB Adapter, complete the following steps: 1. At the Main Menu prompt, type H. The activity history for the adapter is displayed. UDBAgent 4.6 Agent Request Statistics Date Add Mod Del Ssp Res Rec /15/ X. Done 2. Type X to return to the Main Configuration Menu. Accessing help and additional options In order to access the agentcfg help menu and use the help arguments, complete the following steps: 1. At the Main Menu prompt, type X. The command prompt is displayed, and you are in the \bin directory. 2. Type agentcfg -help at the prompt to view the help menu. The following list of possible commands is displayed: -version ; Show version -hostname < value> ; Target nodename to connect to (Default:Local host IP address) -findall ; Find all agents on target node -list ; List available agents on target node -agent <value> ; Name of agent -tail ; Display agent s activity log -schema ; Display agent s attribute schema -portnumber <value>; Specified agent s TCP/IP port number -netsearch <value> ; Lookup agents hosted on specified subnet -confidencetest ; Confidence test -setup ; Confidence test setup -help ; Display this help screen Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 25

40 Table 12 describes each argument. Table 12. Arguments and descriptions for the agentcfg help menu Argument Description -version Use this argument to display the version of the agentcfg tool. -hostname <value> Use the -hostname argument with any of the following arguments to specify a different host: v v v v -findall -list -tail -agent Enter a host name or IP address as the value. -findall Use this argument to search and display all port addresses between and and their assigned adapter names. This option will timeout on unused port numbers, so it might take several minutes to complete. Add the -hostname argument to search a remote host. -list Use this argument to display the adapters that are installed on the local host of the UDB Adapter. By default, the first time you install an adapter, it is either assigned to port address or to the next available port number. All subsequently installed adapters are then assigned to the next available port address. Once an unused port is found, the listing stops. Use the -hostname argument to search a remote host. -agent <value> Use this argument to specify the adapter that you want to configure. Enter an adapter name as the value. Use this argument with the -hostname argument to modify the configuration setting from a remote host. You can also use this argument with the -tail argument. -tail Use this argument with the -agent argument to display the activity log for an adapter. Add the -hostname argument to display the log file for an adapter on a different host. -schema This option is no longer supported. -portnumber <value> Use this argument with the -agent argument to specify the port number that is used for connections for the agentcfg tool. -netsearch <value> Use this argument with the -findall argument to display all active adapters on the system. You must specify a subnet address as the value. -confidencetest Use this argument to run a test to add, modify, search, and delete a request to the adapter. The confidence test allows you to test the connection between the adapter and the UDB RDBMS. This allows you to verify that the adapter can connect to UDB RDBMS without the Tivoli Identity Manager Server. -setup Use this argument, along with the confidence argument, to configure the confidence test. -help Use this argument to display the Help information for the agentcfg command. 26 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

41 3. Type agentcfg and one or more of the supported arguments at the prompt. You must type agentcfg before every argument to run the adapter configuration tool. Type agentcfg -list to list all of the adapters on the local host IP address. Note that the default node for the Tivoli Identity Manager Server is The output is similar to the following output: Agent(s) installed on node UDBAgent (44970) Type agentcfg -agent UDBAgent to display the Main Menu of the agentcfg tool, which is used to view or modify the UDB Adapter parameters. Type agentcfg -list -hostname to list the adapters on a host whose IP address is Note that the default node for the UDB Adapter is The output is similar to the following output: Agent(s) installed on node UDBAgent (44970) Type agentcfg -agent UDBAgent -hostname to display the Main Menu of the agentcfg tool for a host whose IP address is Use the menu options to view or modify the UDB Adapter parameters. Chapter 3. Configuring the UDB adapter for IBM Tivoli Identity Manager 27

42 28 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

43 Chapter 4. Configuring SSL authentication for the UDB adapter In order to establish a secure connection between a Tivoli Identity Manager adapter and the Tivoli Identity Manager Server, you must configure the adapter and the server to use the Secure Sockets Layer (SSL) authentication with the default communication protocol, DAML. By configuring the adapter for SSL, you ensure that the Tivoli Identity Manager Server verifies the identity of the adapter before a secure connection is established. You can configure SSL authentication for connections that originate from the Tivoli Identity Manager Server or from the adapter. Typically, the Tivoli Identity Manager Server initiates a connection to the adapter in order to set or retrieve the value of a managed attribute on the adapter. However, depending on the security requirements of your environment, you might need to configure SSL authentication for connections that originate from the adapter. For example, if the adapter uses events to notify the Tivoli Identity Manager Server of changes to attributes on the adapter, you can configure SSL authentication for Web connections that originate from the adapter to the Web server used by the Tivoli Identity Manager Server. In a production environment, you need to enable SSL security; however, for testing purposes you might want to disable SSL. If an external application that communicates with the adapter (such as the Tivoli Identity Manager Server) is set to use server authentication, you must enable SSL on the adapter to verify the certificate that the application presents. This chapter presents an overview of SSL authentication, certificates, and how to enable SSL authentication using the CertTool utility. Overview of SSL and digital certificates When you deploy Tivoli Identity Manager in an enterprise network, you must secure communication between the Tivoli Identity Manager Server and the software products and components with which the server communicates. The industry-standard SSL protocol, which uses signed digital certificates from a certificate authority (CA) for authentication, is used to secure communication in a Tivoli Identity Manager deployment. Additionally, SSL provides encryption of the data exchanged between the applications. Encryption makes data transmitted over the network intelligible only to the intended recipient. Signed digital certificates enable two applications connecting in a network to authenticate each other s identity. An application acting as an SSL server presents its credentials in a signed digital certificate to verify to an SSL client that it is the entity it claims to be. An application acting as an SSL server can also be configured to require the application acting as an SSL client to present its credentials in a certificate, thereby completing a two-way exchange of certificates. Signed certificates are issued by a third-party certificate authority for a fee. Some utilities, such as those provided by OpenSSL, can also issue signed certificates. A certificate-authority certificate (CA certificate) must be installed to verify the origin of a signed digital certificate. When an application receives another application s signed certificate, it uses a CA certificate to verify the originator of Copyright IBM Corp. 2002,

44 the certificate. A certificate authority can be well-known and widely used by other organizations, or it can be local to a specific region or company. Many applications, such as Web browsers, are configured with the CA certificates of well known certificate authorities to eliminate or reduce the task of distributing CA certificates throughout the security zones in a network. Private keys, public keys, and digital certificates Keys, digital certificates, and trusted certificate authorities are used to establish and verify the identities of applications. SSL uses public key encryption technology for authentication. In public key encryption, a public key and a private key are generated for an application. Data encrypted with the public key can only be decrypted using the corresponding private key. Similarly, the data encrypted with the private key can only be decrypted using the corresponding public key. The private key is password-protected in a key database file so that only the owner can access the private key to decrypt messages that are encrypted using the corresponding public key. A signed digital certificate is an industry-standard method of verifying the authenticity of an entity, such as a server, client, or application. In order to ensure maximum security, a certificate is issued by a third-party certificate authority. A certificate contains the following information to verify the identity of an entity: Organizational information Public This section of the certificate contains information that uniquely identifies the owner of the certificate, such as organizational name and address. You supply this information when you generate a certificate using a certificate management utility. key The receiver of the certificate uses the public key to decipher encrypted text sent by the certificate owner to verify its identity. A public key has a corresponding private key that encrypts the text. Certificate authority s distinguished name The issuer of the certificate identifies itself with this information. Digital Self-signed signature The issuer of the certificate signs it with a digital signature to verify its authenticity. This signature is compared to the signature on the corresponding CA certificate to verify that the certificate originated from a trusted certificate authority. Web browsers, servers, and other SSL-enabled applications generally accept as genuine any digital certificate that is signed by a trusted certificate authority and is otherwise valid. For example, a digital certificate can be invalidated because it has expired or the CA certificate used to verify it has expired, or because the distinguished name in the digital certificate of the server does not match the distinguished name specified by the client. certificates You can use self-signed certificates to test an SSL configuration before you create and install a signed certificate issued by a certificate authority. A self-signed certificate contains a public key, information about the owner of the certificate, and the owner s signature. It has an associated private key, but it does not verify the origin of the certificate through a third-party certificate authority. Once you 30 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

45 generate a self-signed certificate on an SSL server application, you must extract it and add it to the certificate registry of the SSL client application. This procedure is the equivalent of installing a CA certificate that corresponds to a server certificate. However, you do not include the private key in the file when you extract a self-signed certificate to use as the equivalent of a CA certificate. Use a key management utility to generate a self-signed certificate and a private key, to extract a self-signed certificate, and to add a self-signed certificate. Where and how you choose to use self-signed certificates depends on your security requirements. In order to achieve the highest level of authentication between critical software components, do not use self-signed certificates, or use them selectively. For example, you can choose to authenticate applications that protect server data with signed digital certificates, and use self-signed certificates to authenticate Web browsers or Tivoli Identity Manager adapters. If you are using self-signed certificates, in the following procedures you can substitute a self-signed certificate for a certificate and CA certificate pair. Certificate and key formats Certificates and keys are stored in files with the following formats:.pem format A privacy-enhanced mail (.pem ) format file begins and ends with the following lines:.arm.der -----BEGIN CERTIFICATE END CERTIFICATE----- The use of SSL authentication A.pem file format supports multiple digital certificates, including a certificate chain. If your organization uses certificate chaining, use this format to create CA certificates. format An.arm file contains a base-64 encoded ASCII representation of a certificate, including its public key, but not its private key. An.arm file format is generated and used by the IBM Key Management utility. format A.der file contains binary data. A.der file can only be used for a single certificate, unlike a.pem file, which can contain multiple certificates..pfx format (PKCS12) A PKCS12 file is a portable file that contains a certificate and a corresponding private key. This format is useful for converting from one type of SSL implementation to a different implementation. For example, you can create and export a PKCS12 file using the IBM Key Management utility, then import the file to another machine using the CertTool utility. When you start the adapter, the available connection protocols are loaded. The DAML protocol is the only available protocol that supports the use of SSL authentication. You can specify to use the DAML SSL implementation. The DAML SSL implementation uses a certificate registry to store private keys and certificates. The location of the certificate registry is managed internally by the Chapter 4. Configuring SSL authentication for the UDB adapter 31

46 CertTool key and certificate management tool; therefore, you do not specify the location of the registry when you perform certificate management tasks. For more information on the DAML protocol, see Changing protocol configuration settings on page 10. Configuring certificates for SSL authentication Use the following procedures to configure the adapter for one-way or two-way SSL authentication using signed certificates. In order to perform these procedures, use the CertTool utility. Configuring certificates for one-way SSL authentication In this scenario, the Tivoli Identity Manager Server and the Tivoli Identity Manager adapter are set to use SSL. Client authentication is not set on either application. The Tivoli Identity Manager Server operates as the SSL client and initiates the connection. The adapter operates as the SSL server and responds by sending its signed certificate to the Tivoli Identity Manager Server. The Tivoli Identity Manager Server uses the CA certificate that is installed to validate the certificate sent by the adapter. In Figure 2, Application A operates as the Tivoli Identity Manager Server, and Application B operates as the Tivoli Identity Manager adapter. Tivoli Identity Manager Server (SSL client) 1 Hello Tivoli Identity Manager adapter (SSL server) C Keystore CA Certificate A Verify Send Certificate B Certificate A Figure 2. One-way SSL authentication (server authentication) In order to configure one-way SSL, perform the following tasks for each application: 1. On the adapter, complete these steps: a. Start the CertTool utility. b. In order to configure the SSL-server application with a signed certificate issued by a certificate authority: 1) Create a certificate signing request (CSR) and private key. This step creates the certificate with an embedded public key and a separate private key and places the private key in the PENDING_KEY registry value. 2) Submit the CSR to the certificate authority using the instructions supplied by the CA. When you submit the CSR, specify that you want the root CA certificate returned with the server certificate. 2. On the Tivoli Identity Manager Server, complete one of these steps: 32 IBM Tivoli Identity Manager: DB2 Universal Database Adapter Installation and Configuration Guide

47 v If you are configuring the use of a signed certificate issued by a well-known CA, ensure that the Tivoli Identity Manager Server has stored the root certificate of the CA (CA certificate) in its keystore. If the keystore does not contain the CA certificate, extract the CA certificate from the adapter and add it to the keystore of the server. v If you are configuring the use of self-signed certificates: If you generated the self-signed certificate on the Tivoli Identity Manager Server, the certificate is already installed in its keystore. If you generated the self-signed certificate using the key management utility of another application, extract the certificate from that application s keystore and add it to the keystore of the Tivoli Identity Manager Server. Configuring certificates for two-way SSL authentication In this scenario, the Tivoli Identity Manager Server and the Tivoli Identity Manager adapter are set to use SSL and the adapter is set to use client authentication. Once sending its certificate to the Tivoli Identity Manager Server, the adapter requests identity verification from the server, which sends its signed certificate to the adapter. Both applications are configured with signed certificates and corresponding CA certificates. In Figure 3, the Tivoli Identity Manager Server operates as Application A, and the Tivoli Identity Manager adapter operates as Application B. Tivoli Identity Manager Server (SSL client) Keystore CA Certificate A Verify Hello Send Certificate A Tivoli Identity Manager adapter (SSL Cserver) Certificate A C Send Certificate A Certificate B Verify CA Certificate B Send Certificate B Figure 3. Two-way SSL authentication (client authentication) The following procedure assumes that you have already configured the adapter and Tivoli Identity Manager Server for one-way SSL authentication using the procedure described in Configuring certificates for one-way SSL authentication on page 32. Therefore, if you are using signed certificates from a CA: v The adapter is configured with a private key and a signed certificate that was issued by a CA. v The Tivoli Identity Manager Server is configured with the CA certificate of the CA that issued the signed certificate of the adapter. In order to complete the certificate configuration for two-way SSL, perform the following tasks: Chapter 4. Configuring SSL authentication for the UDB adapter 33