IBM Tivoli Identity Manager IBM Tivoli Access Manager Combo Adapter 5.0.14 is available. Compatibility, installation, and other getting-started issues are addressed.
Welcome to the IBM Tivoli Identity Manager IBM Tivoli Access Manager Combo Adapter.
These Release Notes contain information for the following products that was not available when the IBM Tivoli Identity Manager manuals were printed:
· IBM Tivoli Identity Manager IBM Tivoli Access Manager Combo Adapter Installation and Configuration Guide
The IBM Tivoli Access Manager Combo Adapter is designed to create and manage accounts on the IBM Tivoli Access Manager for e-business (TAM). The adapter runs in "agentless" mode and communicates using ITAM API and LDAP protocol to the systems being managed.
IBM recommends the installation of this adapter (and the prerequisite Tivoli Directory Integrator) on each node of an Identity Manager WAS cluster. A single copy of the adapter can handle multiple Tivoli Identity Manager 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 Identity Manager Provisioning Policies and Approval Workflow process. Please refer to the Identity Manager Information Center for a discussion of these topics.
The Identity Manager adapters are powerful tools that require Administrator Level authority. Adapters operate much like a human system administrator, creating accounts, permissions and home directories. Operations requested from the Identity Manager server will fail if the adapter is not given sufficient authority to perform the requested task. IBM recommends that this adapter run with administrative (root) permissions.
Adapter Version
|
Component |
Version |
|
Release Date |
December 30, 2011 |
|
Adapter Version |
5.0.14 |
|
Component Versions |
Adapter build: 5.0.14.53 Profile: 5.0.14.53 Connector: 5.0.14.53 Dispatcher 5.017 |
|
Documentation |
Tivoli Access Manager Combo Adapter Installation and Configuration Guide GC23-8805-03 |
New Features
|
Enhancement # (FITS) |
Description |
|
|
Items included in current release |
|
INT47934 |
Support TAM 6.1 for Registry Direct API based recons.
Note: Please contact TAM support to obtain the required Registry Direct API jar file and configuration instructions.
|
|
INT47711 |
Merge adapter profiles into one.
Note: itamprofile.jar can now be used for both AD and non-AD TAM environments. See "Known Issues" section for a profile installation issue they may affect some environments.
|
|
INT45044 |
Improve performance of change password operation requiring multiple SSO cred updates.
|
|
INT44852 |
Add TAM Combo dispatcher parameters tab.
|
|
INT47645 |
Improve documentation around deletion of group membership when deleting TAM account.
|
|
MR0304096333 |
TAM Connector: TAM account password change performs unnecessary group attribute processing.
|
|
|
Items included in 5.0.13 version |
|
MR0824091226 |
Allow GSO credentials to be removed from ITAM account without recon.
See "Known Limitations" section for more detail.
|
|
INT34391 |
Update Release Notes to support the common ITIM Adapter format.
|
|
MR0523115431 |
The debug lines for eritamldapconndebug and eritamtamconndebug should be uncommented in service.def.
|
|
INT033636 |
Performance increase.
See "Appendix B. Performance optimization" of Tivoli Access Manager Combo Adapter Installation and Configuration Guide for more detail.
|
|
MR0121114310 |
TAM Combo: Enhance TAM Combo Adapter Reconciliation performance.
See "Appendix B. Performance optimization" of Tivoli Access Manager Combo Adapter Installation and Configuration Guide for more detail.
|
|
MR0603116412 |
Recons are slow when there are groups with large memberships.
See "Appendix B. Performance optimization" of Tivoli Access Manager Combo Adapter Installation and Configuration Guide for more detail.
|
|
MR0820104534 |
When un-checking GSO User, and removing a credential gets warning.
|
|
INT000068 |
Support for ITDI 7.1.
Note: As a result, the installation instruction for the adapter has changed. See "Tivoli Access Manager Combo Adapter Installation and Configuration Guide" for more detail.
|
|
INT000023 |
TAM API & LDAP Recon get single value cn.
Note: LDAP API based reconciliation is now deprecated hence the required change was implemented only for TAM API and Registry Direct API based reconciliations.
|
|
MR0225115739 |
TAMCombo Adapter always running full reconciliation against TAM
Note: LDAP API based reconciliation is now deprecated hence the required change was implemented only for TAM API and Registry Direct API based reconciliations.
|
Closed Issues
|
CMVC# |
APAR# |
PMR# / Description |
|
|
|
Items closed in current version |
|
|
IV11692 |
TAM Combo Adapter does not handle "\", backslash, in TAM DN.
|
|
|
IV09586 |
Account with uppercase CN not reconciled using "TAM Registry Direct API"
|
|
|
|
Items closed in 5.0.13 version |
|
103752 |
|
TDI Dispatcher text field incorrectly documented as optional.
|
|
|
|
Items closed in 5.0.12 version |
|
|
|
None.
|
|
|
|
Items closed in 5.0.11 version |
|
|
|
Updated release notes to refer to the Installation Guide (MR042110398).
|
|
98115 |
IZ68193 |
Documentation update - The adapter does not support the modify of CN, UID or principal name
|
|
100659 |
IZ74337 |
ITDI JavaScript error during change password results in requests hung in pending state in ITIM.
|
|
36239 |
|
PMR 54834,033,000 / Clarify ITAM JRTE configuration process.
|
|
|
IZ51203 |
TAM Combo always change password, even if eritamssosync is set to false.
|
|
94235 |
IZ63674 |
PMR 91781,7TD,000,12428,227,000 / ITAM Combo looks up all users during a group modify
|
Known Issues
|
CMVC# |
APAR# |
PMR# / Description |
|
|
95735 |
|
|
|
|
85051
|
N/A |
When using the ITAM API method of reconciliation to reconcile ITAM accounts, if an ITAM account already in the ITIM registry becomes a malformed ITAM account then ITIM will identify this malformed ITAM account as no longer existing, and delete it from the ITIM registry. If the malformed ITAM account does not already exist within ITIM's known ITAM accounts, the account will not be added. This behavior does not provide any warning or failure message by ITIM. See Installation guide how to change configuration regarding this issue.
|
|
|
|
|
During the creation of ITAM accounts when ITAM is configured against Windows Active Directory, the account is created as a GSO user even when the Single Signon Capability for the account is not checked (i.e. There is no request to create the account as a GSO user). This is a reflection of the operation of ITAM when administrating accounts. If GSO credentials are supplied with same request they will be created without warning that ITAM account doesn't have Single Signon Capability.
|
|
|
93688
|
|
When ITAM is configured against Windows Active Directory ITAM account's common name (cn) must be the same as the first RDN value of the Distinguished Name. For example, when requesting a new ITAM Combo service account through the ITIM web console, the "Full name" specified in the Account form must be the same as the "cn" portion of the Distinguished Name. E.g. If a user has the Distinguished Name cn=JohnSmith,o=myCompany,c=com, then the "Full name" should also be set to JohnSmith. Not doing so could result in account modification issues.
|
|
|
|
|
Adapter doesn't check syntax for any non-TAM account attributes. This can result in those attributes not being set in the registry if their values have incorrect syntax. A possible consequence is that operations such as account creation may fail.
|
|
|
|
|
In case that an account already has SSO credentials and checkbox Single Signon Capability is disabled during MODIFY operation, this will delete credentials in ITAM registry, but not in ITIM. The reconciliation is needed to synchronize the account attributes.
|
|
|
|
|
If password synchronization is configured to synchronize passwords from WebSEAL via ITIM to other person accounts, the synchronization with SSO credential passwords is not supported. The synchronization with SSO credential passwords is supported only if the password change is initiated from ITIM, and the corresponding TDI Assembly Line is executed.
|
|
|
If password synchronization is configured to synchronize passwords from WebSEAL the "Change password on next login" checkbox on the account form cannot be reset. This is due to a current limitation of the ITIM Server.
|
|||
|
|
|
Due to the effort to merge two profiles into one, LDAP schema OID of an existing attribute had to change. When upgrading the adapter profile to 5.0.14 or later from 5.0.13 or earlier, the following change needs to be made in <tds_instance_home>/etc/V3.modifiedschema of TIM's directory server prior to installing the new profile.
Change
( 1.3.6.1.4.1.6054.3.141.2.35 NAME 'eritamgroupcn' DESC 'TAM Group CN' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
to
( 1.3.6.1.4.1.6054.3.141.2.37 NAME 'eritamgroupcn' DESC 'TAM Group CN' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
The directory server needs to be restarted after making this change. If the above steps are not made prior to installing the new profile then the installation may fail with the following error message in TIM's msg.log or trace.log:
Failed to Modify Attribute eritamgroupcn: [LDAP: error code 16 - GLPSCH027E attribute type '1.3.6.1.4.1.6054.3.141.2.37' does not exist; replace operation failed. |
Known Limitations
|
CMVC# |
APAR# |
PMR# / Description |
|
|
|
The adapter does not support using multiple values for CN during the account add operation due to limitations in TAM API. The default account form uses an editable text list but this is for displaying reconciled CN values only in support of the feature INT000023.
|
|
|
|
The adapter does not support the modification of UID, CN, principal name, and attribute(s) that form the Distinguished Name(DN).
|
|
|
|
Custom containers are not supported when creating an ITAM group. ITAM specifies a default
|
|
|
|
Filtered reconciliation on groups is not supported.
|
|
|
|
When "Single Signon Capability" attribute is unchecked and an account modification request is submitted, the SSO credentials for the account are removed in ITAM but this is not reflected in ITIM. This is due to the RMI protocol not allowing the response to contain the updated account information. In order to work around this limitation, edit the "modify" operation workflow for "TAM Account" entity to delete "eritamcred" attribute when "eritamsinglesign" attribute is set to "false". For example, add a script element with the following script before "MODIFYACCOUNT" extension:
var accountObj = account.get(); var changes = account.get().getChanges(); if (changes != null && changes.length > 0) { for (i =0 ; i < changes.length ; i++) { if (changes[i].attr == "eritamsinglesign" && changes[i].values[0] == "false") { accountObj.removeProperty("eritamcred"); account.set(accountObj); } } }
Alternatively, a subsequent reconciliation will correct the account information in ITIM. |
Known ITIM Issues
|
CMVC# |
APAR# |
PMR# / Description |
|
|
|
The adapter does not support the modification of UID, CN, principal name, and attribute(s) that form the Distinguished Name(DN).
|
|
|
|
Custom containers are not supported when creating an ITAM group. ITAM specifies a default
|
|
|
|
Filtered reconciliation on groups is not supported.
|
Known ITAM Issues
|
CMVC# |
APAR# |
PMR# / Description |
|
|
|
When the Single Signon Capability of a ITAM user account is disabled (i.e. the user is no longer a GSO user), the GSO resource credentials for that account are also deleted. Hence when disabling the Single Signon Capability for a ITAM Combo user account from ITIM, attempting to delete or modify resource credentials in the same request for that account results in "successful with warning" as the GSO credentials cannot be found.
|
|
|
|
TAM Java Admin API does not provide for a CN to be specified when creating a group. This is reflected in the adapter which does not manage this attribute when adding or modifying groups.
|
|
|
|
If ITAM is configured against Windows Active Directory, an existing user or group description cannot be modified to a blank value. The description will remain unchanged.
|
|
|
|
If ITAM is configured against Windows Active Directory, when importing an account using the pdadmin command line, the user name and first RDN value of the user DN must be the same. This issue is reflected in the adapter: User ID and first RDN value in the user Distinguished Name must be the same.
|
|
|
|
If ITAM is configured against IBM Tivoli Directory Server 6.0, Fix Pack 5 must be installed on the Directory Server. This fix pack addresses a problem that may affect adapter operation (APAR IO06328).
|
See the IBM Tivoli Identity Manager Adapter Installation Guide for detailed instructions.
Corrections to Installation Guide
The following corrections to the Installation Guide apply to this release:
None.
Configuration Notes
The following configuration notes apply to this release:
None.
The Identity Manager 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:
Note: If the customization requires a new Tivoli Directory Integrator connector, the developer must also be familiar with Tivoli Directory Integrator connector development and working knowledge of Java programming language.
Tivoli Identity Manager Resources:
Check the "Training" section of the Tivoli Identity Manager Support web site for links to training, publications, and demos.
Tivoli Directory Integrator Resources:
Check the "Training" section of the Tivoli Directory Integrator Support web site for links to training, publications, and demos.
Support for Customized Adapters
The integration to the Identity Manager server "the adapter framework" is supported. However, IBM does not support the customizations, scripts, or other modifications. If you experience a problem with a customized adapter, IBM Support may require the problem to be demonstrated on the GA version of the adapter before a PMR is opened.
Installation Platform
The IBM Tivoli Identity Manager Adapter was built and tested on the following product versions.
Adapter Installation Platform:
Managed Resource:
Please note that some ITAM versions are not supported on some JREs associated with some Operating Systems. Please see the ITAM Combo Installation Guide for further information.
IBM Tivoli Identity Manager:
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
The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, IBM logo, AIX, DB2, Domino, Lotus, Tivoli, Tivoli logo, Universal Database, WebSphere, i5/OS, RACF.
Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.
Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer Entertainment, Inc., in the United States, other countries, or both and is used under license therefrom.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. 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.
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.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the U.S., 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.
IT Infrastructure Library® is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.
Other company, product, and service names may be trademarks or service marks of others.