IBM Security Verify Governance Adapter 10.0.3 for Amazon Web Services - Release notes

IBM Security Verify Governance Adapter 10.0.3 for AWS 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

1. Preface. 1

2. Adapter Features and Purpose. 3

3. License Agreement. 2

4. Service Groups Management. 2

5. Contents of this Release. 4

Adapter Version

New Features

Closed Issues

Known limitations

6. Installation and Configuration Notes. 9

7. Customizing or Extending Adapter Features. 10

Getting Started

Support for Customized Adapters

8. Supported Configurations. 11

9. Notices. 12

Preface

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

· IBM Security Verify Governance Adapter for AWS Installation and Configuration guide

Adapter Features and Purpose

The IBM Security Verify Governance Adapter for AWS is designed to operate several administrative tasks on the Amazon Web Services (AWS) Identity and Access Management

This adapter (and the prerequisite IBM Security Directory Integrator) should be installed for each node of an IBM Security Verify Governance WebSphere cluster. A single copy of the adapter can handle multiple IBM Security Verify Governance services.

IBM Security Verify Governance adapters are powerful tools that require Administrator Level authority. Adapters operate creating console access accounts, groups and policies. 

Service Groups Management

A service group refers to any logical entity that can group accounts together on the managed resource. In the case of IBM Security Verify Governance Adapter for AWS, the service group is an AWS group, role and policies.

Managing service groups implies the following:

·      Retrieve service groups on the managed resource.

·      Add users to AWS group or Attach AWS policies to user.

·      Remove users from AWS group or detach AWS policies from user.

Note:  Modify service group name is not supported.

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
Release Date	2025 December 18 21.41.11
Adapter Version	10.0.3
Component Versions	Adapter build: 10.0.3.10 Profile:  10.0.3.10 Connector:  10.0.3.10
Documentation	The following guide is available in the IBM Knowledge Center IBM Security Verify Governance Adapter for AWS Installation and Configuration guide

New Features

Internal#	RFE/CASE#	Description
		Items included in current 10.0.3 release
SVGAD-5516	ADAPT-236	Certify the adapter for use with IBM Verify Identity Governance version 11.x
SVGAD-5558	ADAPT-231	Certify the adapter for use with SDI 10
		Items included in 10.0.2 release
SVGAD-177	ADAPT-I-201	AWS Adapter to support AssumeRole.
JIRA SVGAD-163		Added the adapter support to use temporary security credentials for authentication and connection to AWS IAM.
JIRA SVGAD-177		Added the adapter support to use access key id,secret access key and session token generated using AssumeRole API for authentication.
		Items included in 10.0.1 release
JIRA SVGAD-162		Added the adapter support for aws-java-sdk 2.0 jar with package names changes and code changes
		Items included in 7.1.5 release
RTC 190586		Certification: Testing and Document Update AWS adapter for Redshift
RTC 181496		Supporting data changes for IGI 5.2.5 - Attribute Values Lookup Support
		Items included in 7.1.4 release
		None
		Items included in 7.1.3 release
		None
		Items included in 7.1.2 release
RTC 167542		US - As an AWS adapter developer, I must support AWS service accounts. More details about ‘Service Accounts’ are available at Creating accounts with Programmatic Access
INTERNAL		Addition of the special flag attribute in targetProfile.json
		Items included in 7.1.1 release
RTC 157156		Support for AWS adapter Service Account Creation And Access Key Management

Closed Issues

Internal#	APAR#	PMR# / Description
		Items included in current 10.0.3 release
		None
		Items included in 10.0.2 release
		None
		Items included in 10.0.1 release
JIRA SVGAD-161		Problem in full reconciliation.It was getting failed with the error:connection refused.
JIRA SVGAD-191		Problem in filter reconciliation.Adapter was fetching all the roles even when the filter eruid=username is given.
JIRA SVGAD-192		Problem in access key generation option for AWS adapter.Access keys were not getting stored in the derby database table
		Items included in 7.1.5 release
		None
		Items included in 7.1.4 release
Internal		Code optimization
		Items included in 7.1.3 release
RTC 167240		Implement "Restore" functionality in AWS adapter to use 'password'
RTC 170843		US - As an AWS IAM adapter developer, I must implement proper error handling and clean up unused code
		Items included in 7.1.2 release
		None
		Items included in 7.1.1 release
		None

Known Limitations

Internal#	APAR#	PMR# / Description
RTC 176821		AWS accounts with Programmatic Access and Console and Programmatic Access are unable to map to IGI users on IGI 524 --Programmatic Access Account has an access key for which Last Used value is N/A if the access key has not been used even once. --This Access key needs to be used at least once and when in AWS the Last Used value for that Account has date value then the IGI users are mapped to the AWS accounts.
RTC 163543		'Add External Role Child' event didn't get triggered in IGI 522 with PostgreSQL

Installation and Configuration Notes

See the IBM Security Verify Governance Adapter for AWS Installation and Configuration guide.

Corrections to Installation Guide:

Chapter 1: Overview

No updates for the current release

Chapter 2: Planning

No updates for the current release

Chapter 3: Installing

 - Installing ILMT-Tags File
  (Please add new section "Installing ILMT-Tags" File under the section Installing > Installing ILMT-Tags in install guide.)

  Before you begin:
   - The Dispatcher must be installed

   Procedure:
   Copy the files in the ILMT-Tags folder to the specified location:
   1. Windows: < SDI-HOME > /swidtag
   2. Unix/Linux: < SDI-HOME >/swidtag

 Installing third-party client libraries
  (Please update section "Installing third-party client libraries" under the section Installing in install guide.)

  -Procedure:
  

  1. Go to the AWS SDK for Java website at https://aws.amazon.com/sdk-for-java/. (See the AWSIAM adapter release notes for the current supported aws-java-sdk version.)
  2. Download the AWS SDK for Java package to a temporary directory.
  3. Extract SDK files.
  4. From the lib directory, copy the file aws-java-sdk.jar into ITDI_HOME\jars\patches directory.
  5. Under third-party\lib, copy all files except spring* jars into ITDI_HOME\jars\patches.See the AWS IAM Adapter Release Notes for these JAR files in the package.
  6. Restart the Dispatcher service.
  For more information about starting and stopping the service, see the Dispatcher Installation and Configuration Guide.

 Service or target form details
  (Please update section "Service or target form details" under the section Installing in install guide.)

 Connection details:
  
  Add this two sections after section "Region"
 
  -AssumeRoleArn
 Role Arn of the role to be assumed.

  -AssumeRole UserName
 Username of the user which have permissions to assume the role.

Installing in the Verify Governance Virtual Appliance

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_ 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 IBM Security Verify Governance Identity Manager Container Starter Kit installation directory, if ISVDI was selected for installation during the ISVG-IM 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 active 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-AWSIAM-*.zip" accept

Where /path/to/adapterUtil.sh is the location where the adapterUtil.sh script could be found is installed and /path/to/Adapter-UnixLinux-*.zip is the location where the Adapter zip file is staged on the machine running Kubernetes cli.

After doing so, follow the given instructions for manually uploading the 3rdparty jars.

Manually copying files to Persistent Volume

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

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

                                 AWSIAMConnector.jar

ILMT-Tags

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

                        ibm.com_IBM_Verify_Identity_Governance_Enterprise-xx.x.x.swidtag

                       ibm.com_IBM_Verify_Identity_Governance_Application-xx.x.x.swidtag

Updating the container

Using Script

To update the dispatcher container with the using the ISVG-IM starter kit , 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

Manually

To update the dispatcher container on Kubernetes/OpenShift, now run the following commands to create a config map and update the dispatcher specific yaml :

<kubectl or oc > create configmap <namespace> --from-file=<path to main isvdi config yaml> --from-file=<directory where certificates are stored> --dry-run=client -o yaml –namespace=<namespace where dispatcher container resides> >  <path_to_dispatcher_container_that_runs_this_adapter_yaml>

e.g.

kubectl create configmap isvgimsdi --from-file=/root/isvg/config/adapters/isvdi_config.yaml --from-file=/root/isvg/config/certs --dry-run=client -o yaml --namespace=isvgim > /root/isvg/yaml/045-config-adapters.yaml

Then apply the updated dispatcher that runs this adapter yaml .

<kubectl or oc> appply -f <path_to_dispatcher_container_that_runs_this_adapter_yaml>

e.g.

oc apply -f /root/isvg/yaml/045-config-adapters.yaml

Finally restart the container

<kubectl or oc> rollout restart deployment <isvdi container deployment>

e.g.

oc -n isvgim rollout restart deployment isvdi

Chapter 4: 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 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
#####################

Configuring the SSL connection between the Dispatcher and the AWS IAM server
  (Please update section "Configuring the SSL connection between the Dispatcher and the AWS IAM server" under the section Configuring in install guide.)

 Procedure:

   Add the below step between step 6 and step 7 -

7. Download the second certificate from the following link : sf-class2-root.crt

Chapter 5: Troubleshooting

  Enabling DEBUG Logs on SDI Server

Procedure:

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">

Post-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

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 <SDI_Solution_Dir>/ibmdiservice.props with below parameter:

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

3. Restart SDI Server process

Chapter 6: Reference

No updates for the current release.

 Customizing or Extending Adapter Features

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

Getting Started

Customizing and extending adapters requires a number of additional skills. The developer must be familiar with the following concepts and skills prior to beginning the modifications:

· IBM Security Verify Governance administration

· IBM Security Directory Integrator management

· IBM 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 IBM Security Directory Integrator connector, the developer must also be familiar with IBM Security Directory Integrator connector development and working knowledge of Java programming language.

IBM Security Verify Governance Resources:

Check the Training section of the IBM Knowledge Centre for links to training, publications, and demos.

IBM Security Directory Integrator Resources:

Check the Learn section of the IBM Tivoli Directory Integrator Support web site for links to training, publications, and demos.

Support for Customized Adapters

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

Supported Configurations

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

Adapter Installation Platform: 

This adapter installs into IBM Security Directory Integrator (SDI) and may be installed on any platform supported by the SDI product and supported by the target system libraries or client, where applicable. IBM recommends installing SDI for each node of the IBM Security Verify Governance WAS Cluster and then installing this adapter on each instance of SDI. Supported SDI versions include:

· Security Directory Integrator 7.2 + FP14

· Security Verify Directory Integrator 10.0 FP5

Note:  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 if you have the entitlement to download IBM Security Directory Integrator 7.2.

Managed Resource:

AWS

aws-java-sdk-2.20.40 or above

            IBM Security Verify Governance:

IBM Security Verify Governance Identity Manager v10.0.x

IBM Security Verify Governance v10.0.x

IBM Verify Identity Governance 11.x

* 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

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.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed.

Trademarks

Other directories that comply with RFC2798 standards and are supported by the IBM Security Directory Integrator LDAP connector. However, you might require additional customization. See the IBM Security Verify Governance Adapter for LDAP Customization Guide for information on customizing this adapter.

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.

End of Release Notes