Release notes - IBM Security Verify Governance 10.0.5 for Google Workspace

IBM Security Verify Adapter v10.0.5 for Google Workspace 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.

 

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 Google Workspace Adapter.

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

·       IBM Security Verify Google Workspace Adapter Installation and Configuration Guide

Adapter Features and Purpose

The Google Workspace Adapter is designed to create and manage User Accounts on the Google Workspace domain. The adapter runs in "agentless" mode and communicates using Google Directory API to the Google Workspace Domain being managed.

IBM Security Verify 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 Verify server will fail if the Adapter is not given sufficient authority to perform the requested task. IBM recommends that this Adapter run with administrative (root) permissions.

License Agreement

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.

Contents of this Release

Adapter Version

Component

Version

Build Date

2025 September 23 04.20.42

Adapter Version

10.0.5

Component Versions

Adapter build: 10.0.5.1

Profile: 10.0.5.1

Connector: 10.0.5.1

Dispatcher 7.0.34 or higher (packaged separately)

aDocumentation

The following guides will be made available in the IBM Knowledge Centre

· Google Workspace Adapter Installation and Configuration Guide

New Features

Internal#

Enhancement # (RFE)

Description

 

 

 Items included in current release (10.0.5)

 SVGAD-4780

ADAPT-199

Support for Custom Multi-Value Attributes in the Google Workspace Adapter

 

 

 Items included in release (10.0.4)

 SVGAD-3064

ADAPT-146

Validate Google Workspace adapter with SDI 10 Container

 

 

 Items included in release (10.0.3)

 

None

 

 

 Items included in release (10.0.2)

 

RTC 189259

Supporting label changes from Google Apps to Google Workspace

 

 

 Items included in release (10.0.1)

 

 

None

 

 

 Items included in 7.1.11 release

 

 

None

 

 

 Items included in 7.1.10 release

 

 

None

 

 

 Items included in 7.1.9 release

 

 

None

 

 

 Items included in 7.1.8 release

 

 

N/A

 

 

 Items included in 7.1.7 release

 

INT154246

Support additional attributes and custom attributes in Google Apps

 

 

 Items included in 7.1.6 release

 

 

Support for IGI 5.2.2

 

 

 Items included in 7.0.5 release

 

INT106146

Implement exponential back-off for "user rate exceeded" error.

 

 

 Items included in 7.0.4 release

 

INT99294

Support non-primary domains.

 

INT99913

Migrate to the new Google Directory API.

 

 

 Items included in 7.0.3 release

 

RFE38223

Support Managing Alias/Nickname.

 

RFE38222

Support Managing Organisation Unit (OU)

 

 

 Items included in 7.0.2 release

 

RFE28276

Support Rename of Google App Account User ID 'eruid' attribute.

 

INT69809

Support Google Data Java Client Library version 1.47.1

 

 

 Items included in 7.0.1 release

 

 

Initial release.

Closed Issues

Internal#

KnownIssue# / Case#

Description

 

 

 Items included in current release (10.0.5)

None

 

 

 Items included in current release (10.0.4)

SVGAD-2496

BUG 4346

 DT393625 /

 TS016223736

Google reconciliation fails after 59 minutes

 

 

 Items included in release (10.0.3)

SVGAD-1268

BUG 4202

 DT257756 /

 TS014297306

Google adapter not returning error back to ISVG when group update fails

 

 

 Items included in release (10.0.2)

 None

 

 

 Items included in release (10.0.1)

RTC 188724

Bug 3475

DOC APAR IJ31796

TS005083303

 correct location/path to download required google apis

 RTC 187873 

Bug 3354

APAR IJ29180

 Problem with Google proxy

 

 

 Items included in 7.1.11 release

 RTC 185053 

Bug 3037

 

 Release Notes - Supported Configurations Incorrect

 

 

 Items included in 7.1.10 release

RTC 182041

 

Internal -GoogleApps adapter Mapping file change for IGI 5.2.5 - eruid target attribute should be mapped to only CODE governance attribute by default

 

 

 Items included in 7.1.9 release

 

RTC  176347

Bug 2575

IJ06784

D - As a GoogleApps adapter developer I need to update the adapter so that it reconciles complete data from multiple domains

 

 

 Items closed in 7.1.8 version

 

 

Work around google defect that causes recon to fail with unexpected error when quota limit is reached

 

 

 Items closed in 7.0.5 version

 

IV57415

The reconciliation gets only 100 accounts (one page).

 

 

 Items closed in 7.0.1 version

 

 

Initial release.

Known Limitations

Internal#

Known Issue#

Case# / Description

 N/A

N/A

Special characters like (*,!) are not supported in reconciliation filter, only exact match values are considered valid for the same.

 N/A

N/A

Character usage (usernames, passwords, names) limitation. Refer to the section "Character usage (usernames, passwords, groups, names)" in Google Workspace Administrator Help.

N/A

N/A

Both the Group ID and User ID are not UTF-8 supported.

 N/A

N/A

Google Data Java Client needs to be copied into the TDI_HOME\jvm\jre\lib\ext\directory.

 N/A

N/A

Group Name cannot be updated during a group modify operation. IBM Security Verify does not allow changing value of the attribute that is mapped to ergroupname.

 N/A

N/A

The existing Group Description cannot be modified to an empty string. This is a known limitation of the Google Workspace Group Provisioning API. The adapter does not accept an empty string or null value.

 N/A

N/A

Adapter does not support NickName.

 N/A

N/A

Adapter does not currently support management of group email permissions as a result of migrating the code to use the Google’s new Directory API.

 N/A

N/A

Adapter does not support Secondary Domain. You have to define the secondary domain as a root domain and define a service for every primary/root domain.

 

Installation and Configuration Notes

             See the IBM Security Verify Governance Application Adapters for SCIM Adapter Installation and Configuration guide.

Corrections and/or additions to the Installation and Configuration sections of the  adapter guide

 

Chapter 1: Overview

             No updates for the current release

 

Chapter 2: Planning

             Prerequisites:

               Directory Integrator:

                          Remove 7.2 + FP6 + 7.2.0-ISS-SDI-LA0019 from the description

                          Identity server:

                          Update description as below:

                                       The following servers are supported:

                                       - IBM Security Verify Governance Identity Manager

                                       - IBM Security Verify Governance

 

Chapter 3: Installing

 

Installing in Virtual Appliance (Chapter present under ISVG only)

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 to install this adapter on the virtual appliance.

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

Descriptions

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

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

·       targetProfile.json

o   Service provider configuration

o   Resource type configuration

o   List of assembly lines

·       A set of assembly lines in XML files

·       A set of forms in XML files

·       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:

·       Connector jar files

·       Configuration files

·       Script files

·       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 and files. 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.

 

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 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 the below command to install / upgrade/ re-install / downgrade the adapter:

/path/to/adapterUtil.sh -loadAdapter "/path/to/Adapter-GoogleWorkspace-*.zip" accept

Where /path/to/adapterUtil.sh is the location where the adapterUtil.sh script is installed and /path/to/Adapter-GoogleWorkspace-*.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:

GoogleAppsConnector.jar

Copy this file to the <Persistent_Volume>/jars/connectors directory.

 

ILMT-Tags

Copy below files to the <Persistent_Volume>/swidtag directory:

 

ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-xxxx.swidtag

ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-xxxx.swidtag

 

P12 file of Google Apps

Copy  this file to the <Persistent_Volume>/timsol/keystores  directory

Using Script

Use the below command to copy the p12 file:

/path/to/adapterUtil.sh -copyFile "/path/to/<test>.p12" "/opt/IBM/svgadapters/timsol/keystores"

 

Import/Add GoogleAppsCustomAttr.txt :

Copy  this file to the <Persistent_Volume>/timsol/  directory

Using Script

Use the below command to copy the GoogleAppsCustomAttr.txt:

/path/to/adapterUtil.sh -copyFile "/path/to/GoogleAppsCustomAttr.txt" "/opt/IBM/svgadapters/timsol/"

 

Copying 3rd party libraries:

Using Script

Use the below command to copy the 3rd party jars:

/path/to/adapterUtil.sh -copyToPatches "/path/to/<jarfile>.jar"

 

E.g. If you want to copy httpclient-10.0.14.jar then use below command, likely copy all other required external jars. List of all required jars with version mentioned in the Supported Configuration > Supported third-part client libraries. Refer to Installing >  Installing third-party client libraries for more details.

 

/path/to/adapterUtil.sh -copyToPatches "/path/to/httpclient-*.jar"

 

This command will copy the 3rd party jars to the <Persistent_Volume>/jars/patches directory.

 

Manually copying files to the Persistent Volume 

            

Copy required 3rd party jar files to the <Persistent_Volume>/jars/patches directory (List of all required jars with version mentioned in the Supported Configuration > Supported third-part client libraries. Refer to Installing >  Installing third-party client libraries for more details.):

 

 

Configuring the SSL connection between the IBM Security Verify Directory Integrator Container and the Google Apps Target

 

Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#keyfile_trusted-certificates page from SVDI

 

If the config.yaml file which is used as the YAML_CONFIG_FILE environment variable for the container doesn't have a trusted-certificates 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#keyfile_trusted-certificates to add a trusted-certificates section to the config.yaml file.

 

To add a trusted-certificates element (if it doesn't exist in current configuration) to the config.yaml file which is used as parameter for YAML_CONFIG_FILE environment variable of the container, download the GTS Root R4 certificates in DER/PEM/CRT format (read instruction in installing > Configuring the SSL connection between the Dispatcher and the Google Apps server) and place the certificate in the certs directory of the config volume which contains the config.yaml file. The default location for this config volume is /opt/IBM/dispatcher/config.

 

Provide this path of the certificate in config.yaml file as shown in the example below:

 

keyfile:

trusted-certificates:

- '@/opt/IBM/dispatcher/config/certs/GTSRootR4.pem'

 

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 to add an advanced configuration element (if it don't exist in current configuration) to the config.yaml file which is used as parameter for YAML_CONFIG_FILE environment variable of the container.

 

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'

 

Enabling debug logs and disabling json-logging

 

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.

 

Refer https://www.ibm.com/docs/api/v1/content/SSCQGF_10.0.0/container/html/verify-directory-integrator.html#general_logging page from SVDI to add root-level and json-logging configuration elements (if they don't exist in current configuration) to the config.yaml file which is used as parameter for YAML_CONFIG_FILE environment variable of the container.

To enable debug logs, set the value for root-level to debug. To disable json logging, set the value for json-logging element to false.

 

Uninstalling the adapter

Using Script

Use the below command to remove the adapter:

 

/path/to/adapterUtil.sh -removeAdapter Adapter-GoogleWorkspace

 

Manually copying / removing files to / from the Persistent Volume

Remove files from the given directory structure of the persistent volume mapped to the /opt/IBM/svgadapters directory of the container image.

Note: Some 3rd party jars and ILMT-Tags files might be common with other installed adapters, and hence should not be removed while uninstalling this adapter:

GoogleAppsConnector.jar

Remove this file from <Persistent_Volume>/jars/connectors directory.

 

ILMT-Tags

Remove below files from <Persistent_Volume>/swidtag directory:

 

ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-xxxx.swidtag

ibm.com_IBM_Verify_Identity_Governance_Application_Adapters-xxxx.swidtag

 

3rd party jars

Remove the appropriate version of the 3rd party jar files used by this adapter as listed in the Supported Configuration > Supported third-part client libraries from the <Persistent_Volume>/jars/patches directory.

 

P12 file of Google Apps

Remove this file from the <Persistent_Volume>/timsol/keystores  directory

 

 

Installing third-party client libraries

                  Procedure

1.      The currently supported version can be found in the release notes for the version of the adapter that you are installing.

2.      Go to the Google Developers website and search for the Google Directory API Java Client Library package that is listed in the Google Workspace Adapter Release Notes.

3.      Go to the Google Developers website and search for the Google Groups Settings API Java Client Library package.

4.       Most other jars can be downloaded from the https://mvnrepository.com website.

5.      The guava be found at: https://mvnrepository.com/artifact/com.google.guava/guava

6.      The gson jar can be found at https://mvnrepository.com/artifact/com.google.code.gson/gson

7.      The commons-codec jar file can be found at https://mvnrepository.com/artifact/commons-codec/commons-codec.

8.      Copy these files into ISVDI_HOME\jars\patches directory.

9.      Restart the Dispatcher service.

10.     For information about starting and stopping the service, see the Dispatcher Installation and Configuration Guide.

  

 

Chapter 4: Upgrading

             Upgrading the adapter binaries or connector

                          Take backup of adapter binaries or connector

                                         Procedure:

                                         Take backup of below files before performing upgrade:

                                         <SDI-HOME>/jars/connectors/GoogleAppsConnector.jar

 

                          Note: Stop the dispatcher service before the upgrading the connector and start it again after the upgrade is complete.

 

                            Upgrade adapter binaries or connector

                                         Procedure:

                                         Copy GoogleAppsConnector.jar from the adapter package to the <SDI-HOME>/jars/connectors directory.

 

             Upgrading the adapter profile

                          Read the adapter Release Notes for any specific instructions before you import a new adapter profile.

                          There is GoogleAppsProfile.jar included in the Google Workspace Adapter distribution package.

 

                          Note: Restart the Dispatcher service after importing the profile. Restarting the Dispatcher clears the assembly lines cache and ensures that the dispatcher runs the assembly lines from the updated adapter profile. 

 

Chapter 5: Configuring

Under Modifying the assembly lines

Procedure (Without Security Directory Integrator Configuration Editor):

  1. Open googleAppsAdd.xml in a text editor after extracting GoogleAppsProfile.jar file into the temporary directory
    • Update googleAppsAdd.xml
      • Locate the AttributeMapItem section and add: 
        <AttributeMapItem>
    <Name>[custom_field_name]</Name>
    <Type>advanced</Type>
    <Script>work.ergoogapps[custom_field_name]</Script>
    <Simple>[custom_field_name]</Simple>
</AttributeMapItem>
      • Locate the SchemaItem section and add: 
        <SchemaItem>
    <Name>[custom_field_name]</Name>
    <NativeSyntax>java.lang.String</NativeSyntax>
</SchemaItem>
  2. Open googleAppsModify.xml in a text editor.
    • Update googleAppsModify.xml
      • Locate the AttributeMapItem section and add: 
        <AttributeMapItem>
    <Name>[custom_field_name]</Name>
    <Type>advanced</Type>
    <Script>work.ergoogapps[custom_field_name]</Script>
    <Simple>[custom_field_name]</Simple>
</AttributeMapItem>
      • Locate the SchemaItem section and add: 
        <SchemaItem>
    <Name>[custom_field_name]</Name>
    <NativeSyntax>java.lang.String</NativeSyntax>
</SchemaItem>
  3. Open googleAppsSearch.xml in a text editor.
    • Update googleAppsSearch.xml
      • Locate the AttributeMapItem section and add: 
        <AttributeMapItem>
    <Name>ergoogapps[custom_field_name]</Name>
    <Type>simple</Type>
    <Simple>[custom_field_name]</Simple>
</AttributeMapItem>

<AttributeMapItem>
    <Name>ergoogapps[custom_field_name]</Name>
    <Type>advanced</Type>
    <Enabled>true</Enabled>
    <Add>true</Add>
    <Modify>true</Modify>
    <Script>conn.[custom_field_name]</Script>
    <Simple>[custom_field_name]</Simple>
</AttributeMapItem>
      • Locate the Output Schema (SchemaItem) section and add: 
        <SchemaItem>
    <Name>[custom_field_name]</Name>
    <NativeSyntax>java.lang.String</NativeSyntax>
</SchemaItem>
  4. Create a jar file with the updated XML files
  5. Import the updated profile.jar into Identity Server

Adapter form modification (optional)

To add Custom Attributes in IGI:

  1. Open targetprofile.json in a text editor.
  2. Locate the userExtension section with the schema: 
    "schema": "urn:ibm:idbrokerage:params:scim:schemas:extension:GoogleAppsAccount:2.0:User"
  3. Add the new attribute definition under attributes for this schema: 
    {
  "name": "ergoogapps[custom_field_name]",
  "type": "string",
  "multiValued": true/false,
  "description": "Description",
  "required": false,
  "caseExact": false,
  "mutability": "readWrite",
  "returned": "default",
  "uniqueness": "none",
  "specialFlags": "none"
}
  4. Save the updated targetprofile.json file.
  5. Create a jar file with updated target profile
  6. Import the updated profile.jar into Identity Server

Create a GoogleAppsCustomAttr.txt file with custom attributes

About this task:   

Note: If you are not using any custom attributes, then, do not define the GoogleAppsCustomAttr.txt file and do not create an empty file with the name GoogleAppsCustomAttr.txt. If custom attribute is multi-valued attribute, then use (:m) at the end of the attribute name. for Example, if the Google Workspace custom field mail_drop is multi-valued, then enter mail_drop:m as a custom field (only for multi valued attribute).

 

Under Schema extensions and custom attributes

Private settings are not supported. The adapter now supports multiple-value custom attributes.

 

Procedure (Without Security Directory Integrator Configuration Editor):

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_Directory>/etc/log4j2.xml

                          3. Modify the following line:

                                      <Root level="info">

                                     to

                                      <Root level="debug">

 

                          From-7.2.0-ISS-SDI-FP0011

                          4. To enable TCB block in debug

                          5. Append the line com.ibm.di.logging.close=false in the  <SDI_HOME_Directory>/etc/global.properties file.

                          

                          6. Start the SDI Server process

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

 

 

                          Logs are not getting printed in FP13 in Windows OS:

                         To fix this issue copy log4j2.xml file from <SDI_Home_Dir>/etc and add to the <SDI_Solution_Dir>/etc (which was missing there). Then configure <SDI_Solution_Dir>/ibmdiservice.props with

                          jvmcmdoptions=-Dlog4j2.configurationFile=etc\log4j2.xml

 

 

Chapter 7: Reference

             No updates for the current release 

 

 

 

 

Customizing or Extending Adapter Features

The IBM Security Verify Governance 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 Verify Governance Adapter Development and Customization Guide

Support for Customized Adapters

The integration to the IBM Security Verify 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

       Supported third-party client libraries:

·      google-api-services-groupssettings-v1-rev20190315-1.27.0

·      google-http-client-1.27.0

·      google-api-client-1.27.0

·      commons-codec-1.11

·      commons-logging-1.2

·      google-api-services-admin-directory-directory_v1-rev118-1.25.0

·      google-http-client-jackson2-1.42.3

·      google-oauth-client-1.34.1

·      google-oauth-client-jetty-1.34.1

·      gson-2.10

·      guava-31.1-jre

·      httpclient-4.5.14

·      httpcore-4.4.16

·      jackson-core-2.14.1

·      jetty-server-11.0.12

·      jetty-util-11.0.12

        Installation Platform

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

       Adapter Installation Platform: 

 

         Due to continuous Java security updates that may be applied to your IBM Security Verify Governance server and IBM Security Verify Governance Identity Manager server, the following SDI releases are the officially supported versions:

              -  Security Directory Integrator 7.2 + FP13

              -  Security Verify Directory Integrator 10.0.0 + LA0002*

              * The Dispatcher version 10.0.2 doesn't support installation using LA0002, please install the Dispatcher10 prior to installing LA0002.     

      Note:  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 adapter's installation and configuration guides for the latest update on IBM Security Directory Integrator versions and fix packs

       

       Managed Resource:

       Google Workspace : Google Workspace Premier, Education, and Partner Edition with Directory API version 1.27

       Google Directory API Java Client Library : 1.27

      Google Groups Settings API Java Client Library: 1.27

 

      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.

 

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.