IBM Security Verify Governance PostgreSQL Adapter 10.0.1 Release notes

IBM Security Verify Governance Adapter PostgreSQL Adapter 10.0.1 is available. Compatibility, installation, and other getting-started issues are addressed.


Copyright International Business Machines Corporation 2003, 2023. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

 

 

Contents

Preface

Adapter Features and Purpose

License agreement

Contents of this Release

Installation and Configuration Notes

Customizing or Extending Adapter Features

Supported Configurations

Notices

 

Preface

Welcome to the IBM Security Verify Governance Adapter PostgreSQL Adapter.

These Release Notes contain information for the following products that was not available when the IBM Security Verify Governance Adapter manuals were printed:

IBM Security Verify Governance Adapter PostgreSQL Adapter Installation and Configuration Guide

 

Adapter Features and Purpose

The PostgreSQL Adapter is designed to create and manage accounts on PostgreSQL Database. The adapter runs in "agentless" mode and communicates using JDBC to the systems being managed.

The Identity Manager Adapters are powerful tools that require Administrator Level authority. Adapters operate much like a human system administrator, creating accounts, permissions and home directories. Operations requested from the Identity Manager server will fail if the Adapter is not given sufficient authority to perform the requested task.

License Agreement

 

Review and agree to the terms of the IBM Security Identity Adapter License prior to using this product.

The license can be viewed from the "license" folder included in the product package.

 

Contents of this Release

Adapter Version

 

Component

Version

Build Date

2023 November 02 03.12.13

Adapter Version

10.0.1

Component Versions

Adapter build: 10.0.1.40

Profile:  10.0.1.40

Connector:  10.0.1.40

Dispatcher 7.1.39 or higher (packaged separately)

Documentation

The following guides are available in the IBM Knowledge Center 

IBM Security Identity Manager adapter for IBM Cloud Identity Installation and Configuration Guide

 

New Features

 

 

Internal#

 

Enhancement # (RFE)

 

Description

 

 

Items included in the current release(10.0.1)

SVGAD-950

 

Verify support for PostgreSQL database version 15

 

 

Items included in the release version 7.1.1

 

 

None

 

Closed Issues

 

Internal#

APAR#

Description

 

 

Items included in the release version 10.0.1

SVGAD-796

 

The input syntax for date and time with timezone is invalid

 

 

Items closed in release version 7.1.1

SVGAD-35

 

The eritdiurl label description is updated to Security Directory Integrator location in the current (new) release

 

Known Limitations

 

Internal#

Idea#

Description

 

 

None

 

 

Installation and Configuration Notes

See the IBM Security Verify Governance Adapter Adapter Installation Guide for detailed instructions.

The PostgreSQL Adapter Installation and Configuration Guide can be obtained from IBM Knowledge Center at https://www.ibm.com/docs/en/svgaa

Corrections to Installation Guide

Chapter 1: Overview

 

No updates for the current release

 

Chapter 2: Planning

 

                          Prerequisites

                           Directory Integrator:
                           Update the description as below:

                           IBM Security Directory Integrator, consult the release notes for the currently supported versions

 

Chapter 3: Installing in the Virtual Appliance

 

                          Installing in the Verify Governance virtual appliance

                  For Verify Governance target management, you can install an IBM Security Verify Governance Adapters or a custom adapter on the built-in Security Directory

                  Integrator in the virtual appliance instead of installing the adapter externally. As such, there is no need to manage a separate virtual machine or system.

 

                          About this task

                       This procedure is applicable for a selected list of Identity Adapters. See the Identity Adapters product documentation to determine which adapters are supported in         Identity Governance and Intelligence, and which can be installed on the virtual appliance.

                       All Identity Governance and Intelligence supported adapters can be installed externally on the virtual appliance. Depending on the adapter, an external Security         Directory Integrator may be required.

                       See the corresponding Adapter Installation and Configuration Guide for the specific prerequisites, installation and configuration tasks, and issues and limitations.

                       See the Adapters Release Notes for any updates to these references.

 

                            Procedure:

                            1. Download the adapter package from the IBM Passport Advantage. For example, Adapter-<Adaptername>.zip. The adapter package includes the following files:

 

                             Table 1. Adapter package contents

                                                                                                                   

 

Files

 

Description

bundledefinition.json

The adapter definition file. It specifies the content of the package, and the adapter installation and configuration properties that are required to install and update the adapter.

Adapter JAR profile

An Security Directory Integrator adapter always include a JAR profile which contains:

a. targetProfile.json

  i. Service provider configuration

  ii. Resource type configuration

  iii. SCIM schema extensions

  iv. List of assembly lines

b. A set of assembly lines in XML files

c. A set of forms in XML files

d. Custom properties that include labels and messages for supported languages.

 

Use the Target Administration module to import the target profile.

Additional adapter specific files

Examples of adapter specific files:

  a. Connector jar files

  b. Configuration files

  c. Script files

  d. Properties files

 

The file names are specified in the adapter definition file along with the destination directory in the virtual appliance

 

                              2. From the top-level menu of the Appliance Dashboard, click Configure > SDI Management.

                              3. Select the instance of the Security Directory Integrator for which you want to manage the adapters and click Manage > SDI Adapters The SDI Adapters window is

                       displayed with a table that list the name, version, and any comments about the installed adapters.

                              4. On the SDI Adapters window, click Install.

                              5. On the File Upload window, click Browse to locate the adapter package and then click OK. For example, Adapter-<Adaptername>.zip.

                              6. Provide the missing 3rd party libraries when prompted.      

                                  a. On the File Upload for Pre-requisite files window, click Select Files. A new File Upload window is displayed.

                                  b. Browse and select all the missing libraries. For example, httpclient-4.0.1.jar

                                  c. Click Open.

                                     The selected files are listed in the File Upload for Pre-requisite files window.

                                  d. Click OK.

                                     The missing files are uploaded and the adapter package is updated with the 3rd party libraries.

                              7.Enable secure communication.      

                                  a. Select the instance of the Security Directory Integrator for which you want to manage the adapter.

                                  b. Click Edit.

                                  c. Click the Enable SSL check box.

                                  d. Click Save Configuration.

                              8. Import the SSL certificate to the IBM® Security Directory Integrator server.      

                                  a. Select the instance of the Security Directory Integrator for which you want to manage the adapter.

                                  b. Click Manage > Certificates.

                                  c. Click the Signer tab.

                                  d. Click Import.

                                     The Import Certificate window is displayed.

                                  e. Browse for the certificate file.

                                  f. Specify a label for the certificate. It can be any name.

                                  g. Click Save.

 

 

Chapter 4: Installing

 

                         Need to add following under Service/Target form details->On the PostgreSQL Connection tab:

         Days password will expire

          The number of days the password is valid.  Allowed value >=0. If this parameter is set on Service form, the password expiration date is set as following.

            No value or 0: the adapter should not change the value of password expiration date.

            Value > 0: the adapter sets the password expiration date to today+Value

          if the password expiration date is explicitely provided for an account , adapter simply sets password expiration date to that value. In that case the expiry date

 

Chapter 5: Upgrading

 

No updates for the current release

 

Chapter 6: Configuring

 

                          Enabling TLSv1.2 in Security Directory Integrator

                                      Procedure:

                                       1. Apply recommended fix packs and limited availability (LA) versions on the Security Directory Integrator. See Recommended fixes for IBM Tivoli Directory                                         Integrator (TDI) & IBM Security Directory Integrator

                                       2. After applying the appropriate updates, modify the /solution.properties file by appending the following text to the bottom of the file:

 

                          #####################

                          # # Protocols to enforce SSL protocols in a SDI Server

                          # # Optional values for com.ibm.di.SSL* property (TLSv1, TLSv1.1, TLSv1.2). # # This can be a multi-valued comma separated property

                          # # This is a single value property.

                          #####################

                          -

                          com.ibm.di.SSLProtocols=TLSv1.1,TLSv1.2

                          com.ibm.di.SSLServerProtocols=TLSv1.1,TLSv1.2

                          com.ibm.jsse2.overrideDefaultProtocol=TLSv12

                          com.ibm.jsse2.overrideDefaultTLS=true

                          #####################

Chapter 7: Troubleshooting

 

                          Enabling DEBUG Logs on SDI Server

                                      Procedure:

                                       1. Stop the SDI Server process

 

                                       Pre-7.2.0-ISS-SDI-FP0008

                                       2. Edit the <SDI_Solution_Directory>/etc/log4j.properties

                                       3. Modify the following line:

                                                   log4j.rootCategory=INFO, Default

                                                   to

                                                   log4j.rootCategory=DEBUG, Default

 

                                      Post-7.2.0-ISS-SDI-FP0008

                                      2. Edit the <SDI_Solution_Directory>/etc/log4j2.xml

                                      3. Modify the following line:

                                                   <Root level="info">

                                                   to

                                                  <Root level="debug">

 

                                      4. Start the SDI Server process

                                      5. Re-create the problem and collect the <SDI_Solution_Dir>/logs/ibmdi.log

 

 

Chapter 8: Uninstalling

 

No updates for the current release

 

Chapter 9: Reference

 

                     Need to add following under Adapter attributes by operations section;Table 13. Test attributes

Required attribute

Optional attribute

erPgSQLPwdDays

None

 

 

 

Configuration Notes

 

            None.

Customizing or Extending Adapter Features

IBM Security Verify Governance Adapter adapters can be customized and/or extended. The type and method of this customization may vary from adapter to adapter.

Refer to the IBM Security Identity Adapter Development and Customization Guide

 

Support for Customized Adapters

The integration to the Identity Manager server the adapter framework is supported. However, IBM does not support the customizations, scripts, or other modifications. If you experience a problem with a customized adapter, IBM Support may require the problem to be demonstrated on the GA version of the adapter before a Case is opened.

 

Supported Configurations

Installation Platform

The IBM Security Verify Governance Adapter Adapter was built and tested on the following product versions.

 

Adapter Installation Platform:

Due to continuous Java security updates that may be applied to your ISIM or PIM servers, the following SDI releases are the officially supported versions:

Security Directory Integrator 7.2 + FP11

Earlier versions of SDI that are still supported may function properly, however to resolve any communication errors, you must upgrade your SDI releases to the officially supported versions by the adapter. 

Managed Resource:

PostgreSQL v12

PostgreSQL v15

IBM Security Verify Governance Adapter:

IBM Security Verify Governance 10.x

IBM Security Verify Governance Identity Manger 10.x

 

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

 

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY  10504-1785  U.S.A.

 

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

 

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

 

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged should contact:

IBM Corporation
2ZA4/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

 

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.