IBM Security Verify Governance Adapter 10.0.1 SAP HANA - Release notes
IBM Security Verify Governance Adapter 10.0.1 for SAP HANA is available. Compatibility, installation, and other getting-started issues are addressed.
Copyright International Business Machines
Corporation 2003, 2025. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
These Release Notes contain information for the following products that was not available when the IBM Security Identity Server manuals were printed:
The IBM Security Verify Governance Adapter for SAP HANA
Database is designed to create and manage accounts on SAP HANA Database. The
adapter runs in "agentless" mode and communicates using JDBC to the
HANA Database being managed.
IBM recommends the installation of this Adapter (and the prerequisite IBM
Security Directory Integrator) on each node of an IBM Security Identity Server
WAS cluster. A single copy of the adapter can handle multiple IBM Security
Identity Server Services. The deployment configuration is based, in part, on
the topology of your network domain, but the primary factor is the planned
structure of your IBM Security Identity Server Provisioning Policies and
Approval Workflow process. Please refer to the IBM
Knowledge Center for a discussion of these topics.
The IBM Security Identity Server 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 IBM Security Identity Server will fail if the Adapter is not
given sufficient authority to perform the requested task. IBM recommends that
this Adapter run with administrative (SYSTEM) permissions.
Review and agree to the terms of the IBM Security Verify Governance Adapter License prior to using this product. The license can be viewed from the "license" folder included in the product package.
Adapter Version
|
Component |
Version |
|
Build Date |
2025 September 16 21.55.43 |
|
Adapter Version |
10.0.1 |
|
Component Versions |
Adapter build: 10.0.1.1 Profile: 10.0.1.1 Connector: 10.0.1.1 Dispatcher 7.1.40 and above (packaged separately) |
|
Documentation |
The following guides are available in the IBM Knowledge Centre: Installation and Configuration Guide for IBM Security Verify Governance Adapter for SAP HANA |
New Feature
|
Internal# |
Enhancement # (RFE) |
Description |
|
|
|
Items included in current release (10.0.1) |
|
SVGAD-4666 |
ADAPT-216 |
Certify the adapter for use with IBM Security Verify Directory Integrator version 10.0.0 |
|
|
|
Items included in 7.1.5 release |
|
|
|
None |
|
|
|
Items included in 7.1.4 release |
|
RTC 174561 |
Verify and Certify SAP HANA 2.02 |
|
|
|
|
Items included in 7.0.3 release |
|
RTC 151784 |
|
Add Support for Identity Governance and Intelligence (IGI) v5.2.2
This adapter is now designed for use with IBM Security Identity Manager, Privileged Identity Manager, and Identity Governance and Intelligence. |
|
|
|
Items included in 7.0.2 release |
|
|
None |
|
|
|
Items included in 7.0.1 release |
|
|
RTC Loading... 142436 |
Certified adapter for SAP HANA Platf. Ed. 1.0 SPS11 (SAP HANA DB 1.00.110) |
|
|
|
Initial Release. |
Closed Issues
|
Internal# |
Case# / APAR# |
PMR# / Description |
|
|
|
Items closed in current release (10.0.1) |
|
SVGAD-3304 BUG 4438 |
|
Unable to assign roles from different Role_Schema to an account |
|
SVGAD-3301 BUG 4440 |
|
In IGI, the password field is not displayed as mandatory attribute on the service form |
|
|
|
Items closed in 7.1.5 release |
|
RTC 182166 |
|
As an SAP Hana Developer, I must ensure that the adapter should assign role, system privileges and application privileges to the User |
|
|
|
Items closed in 7.1.4 release |
|
|
|
None |
|
|
|
Items closed in 7.0.3 release |
|
|
|
None |
|
|
|
Items closed in 7.0.2 release |
|
|
IV86597 |
SAP Hana adapter add operation does not preserve the attributes in ISIM |
|
|
|
Items included in 7.0.1 release |
|
|
Initial Release. |
Known Limitations
|
Internal# |
APAR# |
Case# / Description |
|
|
|
Adapter does not support modifying the user/eruid attribute of SAP HANA |
|
|
|
The following attributes are not supported: Object Privileges, Analytic Privileges, Package Privileges. |
See the Installation and Configuration guide for IBM Security Verify Governance Adapter for SAP HANA Database for detailed instructions.
The SAP HANA Database Adapter Installation and Configuration Guide can be obtained from the IBM Knowledge Center.
Corrections to Install guide:
Chapter 1: Overview
None
Chapter 2: Planning
Prerequisites:
Directory
Integrator IBM Security Directory Integrator
Remove IBM
Security Directory Integrator Version 7.1.1 + 7.1.1-TIV-TDI-FP0004 +
7.2.0-ISS-SDI-LA0008 from the description
Replace "IBM® Security Directory Integrator Version 7.2" in
the description with "Please consult the release notes for the currently
supported versions of the below products".
Remove The adapter supports IBM Security Directory Integrator 7.2,
which is available only to customers who have the correct entitlement. Contact
your IBM representative to find out whether you have the entitlement to
download IBM Security Directory Integrator 7.2. from the note.
Identity
Server IBM Security Verify Governance servers:
Remove existing description and update description as below:
The following servers are supported:
- IBM Verify Identity Governance
- IBM Security Verify Governance Identity Manager
- IBM Security Verify Governance
SAP
HANA version
Remove existing description and update description as below:
Please consult the release notes for the currently supported versions of the
below products
Chapter 3: Installing
Installing
ILMT-Tags File
Before you begin:
The
dispatcher must be installed
Procedure:
Copy the files from ILMT-Tags folder to the specified location:
1. Windows: <SDI-HOME>\swidtag
2. Unix/Linux: <SDI-HOME>/swidtag
Installing
in the virtual appliance(Only for Identity Governance)
Add below note to the end of this chapter:
Note: While
uploading the Adapter package, you may receive System Error: A file
included in the SDI Adapter zip already exists on the system and
the Server Message log under Appliance tab of VA will have a
reference to error com.ibm.identity.sdi.SDIManagementService E File
ibm.com_IBM_Verify_Identity_Governance_xxxx.swidtag found in the adapter zip at
location ILMT-Tags/ already exists in system. This is because, you can
install the same swidtags only once. So, if another adapter of the same type is
installed, remove the swidtags.
The ibm.com_IBM_Verify_Identity_Governance_Enterprise-xxxx.swidtag file
is common to all adapters. In addition to the common swidtag file, an
application adapter needs ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-xxxx.swidtag file
and an infra adapter needs ibm.com_IBM_Verify_Identity_Governance_Lifecycle-xxxx.swidtag and ibm.com_IBM_Verify_Identity_Governance_Compliance-xxxx.swidtag files.
So, if an application adapter is already installed and this is an infra
adapter, then only install the infra-specific swidtags and the other way
around. Please visit Security
Verify Governance Adapters v10.x link to identify the adapter type of
the installed adapters.
Installing
in an IBM Security Verify Directory Dispatcher Container
Before you begin
The steps to install adapter and related
files into the container can be performed using the adapterUtil.sh script,
which is shipped with the dispatcher package. This script should be staged on
the machine running Kubernetes cli. The adapterUtil.sh script is also readily
available in the bin directory of ISIM IBM Security Verify Governance Identity
Manager Container Starter Kit installation directory (If ISVDI was selected for
installation during the ISIM container installation steps).
If, for any reason, the adapter util
script cannot be executed or used, the below manual instructions must be
followed to copy the files to the persistent volume.
Note: The container must
be restarted after installing or uninstalling the adapter and any changes to
the configuration yaml. To activate changes and restart the container run the
following commands:
· <path_to_starterkit>/bin/createConfigs.sh
isvdi
· For OpenShift container: oc -n
isvgim rollout restart deployment isvdi
· For Kubernetes container:
kubectl -n isvgim rollout restart deployment isvdi
Note: This document only
describes the adapterUtil.sh command options that are required to install this
adapter. For other command options, such as listing installed connectors and
3rd party jars, please refer to the Dispatcher10 Installation and Configuration
Guide.
Installing / Upgrading / Re-installing / Downgrading the adapter
Using Script
Use
below command to install / upgrade/ re-install / downgrade the adapter:
/path/to/adapterUtil.sh -loadAdapter "/path/to/Adapter-HANADB-*.zip"
accept
Where
/path/to/adapterUtil.sh is the location where the adapterUtil.sh script is
installed and /path/to/Adapter-HANADB-*.zip is the location where the Adapter
zip file is staged on the machine running Kubernetes cli.
Manually copying files to
Persistent Volume
Copy
the files to the persistent volume mapped to the /opt/IBM/svgadapters directory
of the container image as per the given directory structure:
ILMT-Tags
Copy below files to <Persistent_Volume>/swidtag directory:
- ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-11.0.0.swidtag
- ibm.com_IBM_Verify_Identity_Governance_Enterprise-11.0.0.swidtag
Copying
3rd party libraries:
Using Script
Use
below command to copy 3rd party jar:
/path/to/adapterUtil.sh -copyTo3rdpartyOthers "/path/to/ngdbc.jar"
This
command will copy the 3rd party jars to <Persistent_Volume>/jars/3rdparty/others directory.
Manually copying files to
Persistent Volume
Copy
below 3rd party jar files to <Persistent_Volume>/jars/3rdparty/others directory
(Refer release notes for the supported jar versions):
- ngdbc.jar
Enabling
TLS 1.2
Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced page
from SVDI.
If the config.yaml file which is used as
the YAML_CONFIG_FILE environment variable for the container
doesn't have an advanced configuration element, follow the instructions that
are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#advanced to
add an advanced configuration section to the config.yaml file.
To enable TLSv1.2, add 2 attr and value
(key pair as mentioned in the SVDI guide) as below:
- attr: com.ibm.di.SSLProtocols
value: 'TLSv1.2'
- attr: com.ibm.di.SSLServerProtocols
value: 'TLSv1.2'
Note: The container must
be restarted after making these changes to the configuration yaml. To activate
changes and restart the container run the following commands:
· <path_to_starterkit>/bin/createConfigs.sh
isvdi
· For
OpenShift container: oc -n isvgim rollout restart deployment isvdi
· For
Kubernetes container: kubectl -n isvgim rollout restart deployment isvdi
Enabling debug logs and disabling json-logging
Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#general_logging page
from SVDI.
If the config.yaml file which is used as
the YAML_CONFIG_FILE environment variable for the container
doesn't have root-level and json-logging configuration
elements, follow the instructions that are provided in https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#general_logging to
the add root-level and json-logging configuration
elements section to the config.yaml file.
To enable debug logs, set value for root-level to debug and
to disable json logging, set value for json-logging element
to false.
Note: The container must
be restarted after making these changes to the configuration yaml. To activate
changes and restart the container run the following commands:
· <path_to_starterkit>/bin/createConfigs.sh
isvdi
· For
OpenShift container: oc -n isvgim rollout restart deployment isvdi
· For
Kubernetes container: kubectl -n isvgim rollout restart deployment isvdi
Uninstalling the adapter
Using Script
Use
below command to remove the adapter:
/path/to/adapterUtil.sh -removeAdapter Adapter-SAPHANA
Manually copying files to
Persistent Volume
Remove files from the given directory structure of the persistent volume mapped
to /opt/IBM/svgadapters directory of the container image.
ILMT-Tags
Remove below files from <Persistent_Volume>/swidtag directory:
- ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-11.0.0.swidtag
- ibm.com_IBM_Verify_Identity_Governance_Enterprise-11.0.0.swidtag
3rd party jars
Remove 3rd party jar files used by this
adapter listed below from <Persistent_Volume>/jars/3rdparty/others directory:
- ngdbc.jar
Attribute
Mapping
Remove this chapter for Identity Manager.
Chapter 4: Upgrading
None
Chapter 5: 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 (SDI).
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
# # Optional values for com.ibm.jsse2.overrideDefaultProtocol property
(SSL_TLSv2, TLSv1,TLSv11,TLSv12).
# # This is a single value property.
#####################
-
com.ibm.di.SSLProtocols=TLSv1,TLSv1.1,TLSv1.2
com.ibm.di.SSLServerProtocols=TLSv1,TLSv1.1,TLSv1.2
com.ibm.jsse2.overrideDefaultProtocol=TLSv1
com.ibm.jsse2.overrideDefaultTLS=true
#####################
Customizing
the adapter
The adapters can be customized or extended or both. The type and method of this
customization varies depending on the adapter.
Customizing and extending adapters requires a number of skills. The developer
must be familiar with the following concepts and skills:
- IBM Security Verify Governance Identity Manager administration
-
IBM Security Verify Governance administration
- IBM Security Directory Integrator management
- Security Directory Integrator Assembly Line development
- LDAP schema management
- Working knowledge of Java™ scripting language
- Working knowledge of LDAP object classes and attributes
- Working knowledge of XML document structure
Note: If
the customization requires a new Security Directory Integrator connector, the
developer must also be familiar with Security Directory Integrator connector
development and working knowledge of Java programming language.
Support
for custom adapters
The
integration to IBM Security Verify Governance servers "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 PMR is opened.
Chapter 6:
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_HOME>/etc/log4j2.xml
3. Modify the following line:
<Root level="info">
to
<Root level="debug">
Post-7.2.0-ISS-SDI-FP0011 (To enable TCB block in debug)
4. Append the line com.ibm.di.logging.close=false in the
<SDI_HOME>/etc/global.properties file.
5. Start the SDI Server process
6. Re-create the problem and collect the
<SDI_Solution_Dir>/logs/ibmdi.log
Logs are not getting printed in FP13 in Windows OS
Procedure:
1. Copy log4j2.xml file from <SDI_Home_Dir>/etc and add to the
<SDI_Solution_Dir>/etc (which was missing there).
2. Configure /ibmdiservice.props with below parameter:
jvmcmdoptions=-Dlog4j2.configurationFile=etc\log4j2.xml
3. Restart SDI Server process
Chapter 7: Uninstalling
None
Chapter 8: Reference
None
Installation Platform
The IBM Security Verify Governance Adapter for SAP HANA Database was built and tested on the following product versions.
Adapter Installation Platform:
· IBM Security Directory Integrator 7.2 + FP14
· IBM Security Verify Directory Integrator 10.0.0 + FP5
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 adapters. Please refer to the adapters installation and configuration guides for the latest update on IBM Security Directory Integrator versions and fix packs.
Managed Resource:
· SAP HANA Platf. Ed. 1.0 SPS09 (SAP HANA DB 1.00.91)
· SAP HANA Platf. Ed. 1.0 SPS11 (SAP HANA DB 1.00.110)
· SAP HANA Platf. Ed. 2.0 SPS03 (SAP HANA DB 2.00.030)
Supported third-party client libraries:
· ngdbc.jar: https://mvnrepository.com/artifact/com.sap.hana/ngdbc/2.4
IBM Security Verify Governance Servers:
· IBM Verify Identity Governance v11.0
· IBM Security Verify Governance Identity Manager v10.0
· IBM Security Verify Governance v10.0
*Unless this document specifies a specific fix pack version of ISVG Identity Manager v10, we expect the adapter to work with ISIM 6 as well. However, it will only be debugged and fixed from the perspective of ISVG-IM v10.
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:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
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.
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.
Other company, product, and service names may be trademarks or service marks of others.