IBM Security Identity Adapter for Microsoft Azure Active Directory 7.1.8 is available. Compatibility, installation, and other getting-started issues are addressed.
Copyright International Business Machines Corporation 2003,
2019. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Welcome to the IBM Security Identity Adapter for Microsoft Azure AD.
The Microsoft Azure AD Adapter is designed to create and manage User Accounts on the Microsoft Azure AD domain. The adapter runs in "agentless" mode and communicates using the Windows Azure Active Directory Graph API to the Microsoft Azure Domain being managed.
The IBM Security Identity 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 Governance and Intelligence server will fail if the Adapter is not given sufficient authority to perform the requested task.
Review and agree to the terms of the IBM Security Identity Adapter License prior to using this product. The license can be viewed from the "license" folder included in the product package.
Adapter Version
|
Component |
Version |
|
Build Date |
2020 March 04 09.57.18 |
|
Adapter Version |
7.1.8 |
|
Component Versions |
Adapter build: 7.1.8.24 Profile: 7.1.8.24 Connector: 7.1.8.24 Dispatcher 7.1.39 or higher (packaged separately) |
|
Documentation |
The following guides will be made available in the IBM Identity Adapters Knowledge Center · Microsoft Azure Active Directory Adapter Installation and Configuration Guide |
New Features
|
Internal # |
Enhancement # (RFE) |
Description |
|
|
|
Items included in 7.1.8 release
|
|
|
|
None
|
|
|
|
Items included in 7.1.7 release
|
|
|
|
None
|
|
|
|
Items included in 7.1.6 release |
|
|
167913 |
Azure Roles and Azure Licenses appear as Service Groups.
|
|
|
|
Items included in 7.1.5 release |
|
|
154049 |
Roles are dynamically populated for the given tenant via tha API when creating or modifying a user.
|
|
|
|
Items included in 7.1.4 release |
|
|
|
Add
support for IGI 5.2.2
|
|
|
|
Items included in 7.0.3 release |
|
|
136762 |
Added Configurable parameter to specify the Recon Page Size in Service Form
|
|
|
|
Items included in 7.0.2 release |
|
|
131874 |
Upgraded to Graph API version 1.6, support to the latest version provided by Microsoft.
|
|
|
|
Items included in 7.0.1 release |
|
|
|
Initial Release.
|
Closed Issues
|
Internal# |
APAR# |
Case# / Description |
|
|
|
Items closed in 7.1.8 release
|
|
Bug 3063 |
TS002800844 / Azure AD Adapter error during Change Log Sync operation – Install guide changes only |
|
|
Bug
3088 |
TS002970407 / Adazure recon filter causes odata.error":{"code":"Request_BadRequest"} |
|
|
|
|
Items closed in 7.1.7 release
|
|
RTC 181613
|
|
Facing issue while performing Change Password operation for Azure adapter on IGI 5.2.5. |
|
Internal-RTC 181729
|
|
Internal D - As an Azure Developer, I must ensure that the adapter should create User in Active state when request is from IGI |
|
RTC 179378
|
APAR IJ09099, Bugz 2710
|
D - As an Azure adapter developer, I must ensure that the adapter sends back correct error message when user does not exist during a delete operation |
|
Internal- RTC 181519
|
|
Azure adapter Profile change for IGI 5.2.5 - eruid target attribute should be mapped to CODE governance attribute by default
|
|
|
|
Items closed in 7.1.5 release
|
|
154049 |
|
The 'directoryRoles' segment is used to manage roles instead of 'roles' and objectId to reference roles. This is due to a change in Microsoft API.
|
|
154150 |
52088,800,624/RTC 47191 |
The license removal needs an explicit call to remove the SKU in case no service plans are enabled. This is due to a change in Microsoft API.
|
|
|
|
Items closed in 7.1.4 release
|
|
|
|
Initial Release compliant with IGI 5.2.2
|
|
|
|
Items closed in 7.0.3 release
|
|
135407 |
|
App Key masked in the debug logs
|
|
136311 |
|
License deprovisioning fixed. Only the licenses which are enabled and applicable to User are allowed.
|
|
139239 |
|
ObjectId changed to roleTemplateId due to change in Microsoft API response
|
|
|
|
Items closed in 7.0.2 release
|
|
132799 |
|
The App key is hidden in service form. The attribute "erazureappkey" is added in password.attributes list in enRole.properties in <ISIM_HOME>/data directory.
|
|
|
|
Items closed in 7.0.1 release
|
|
|
|
Initial Release.
|
Known Issues
|
Internal# |
APAR# |
PMR# / Description |
|
N/A |
N/A |
The adapter does not suppport case insensitive filter search with (eruid=username@domainname.com). This is a known issue with the Dispatcher which does filtering during reconciliation. Exact user name will need to be used during filter recon until this issue is fixed in the Dispatcher.
|
|
N/A |
N/A |
The adapter does not support duplicated Group Display Name.
|
|
N/A |
N/A |
The adapter does not support change of Group Name. This is a limitation of the IBM Security Identity Manager. Attempting to change the Group Name will result in the following error: " CTGIMI046E You cannot change the value of the attribute that is mapped to ergroupname."
|
|
N/A |
N/A |
The adapter does not support setting the group attribute 'mailNickName'. This is a limitation of the Windows Azure Active Directory Graph API. The API only accepts 'BposMailNickName' as the value for this attribute during group creation. Any other value will result in the following error: "Invalid value specified for property 'mailNickname' of resource 'Group'".
|
|
N/A |
N/A |
The service principal that represents the adapter service must be in an administrator role that has permissions to modify role objects to send POST or DELETE requests. It must be in a role that has permissions to read role objects to send GET requests. For more information about administrator roles in Windows Azure AD Graph, see Windows Azure AD Graph and Role-Based Access Control. http://msdn.microsoft.com/en-us/library/azure/dn385717.aspx
|
|
N/A |
N/A |
The adapter does not support setting the user account attribute 'mail'. This is a limitation of the Windows Azure Active Directory Graph API. The API consider the 'mail' attribute as a read-only attribute. Trying to set this attribute will result in the following error:"Property 'mail' is read-only and cannot be set."
|
|
N/A |
N/A |
MS API has a limitation that Paging is not supported against roles and querying members of a group. The following documentation highlights the same: http://msdn.microsoft.com/en-us/library/dn727074.aspx#BKMK_Paging
|
|
N/A |
N/A |
Microsoft has a limitation that user accounts cannot be added or modified in a federated domain from an on-premise Dir Sync Active Directory, which is not the default domain. Provisioning of users in such domain can be done by using the AD adapter and then syncing it back to the Azure Directory using the Microsoft DirSync tool.
|
|
N/A |
N/A |
The "Enable detailed TDI debugging" on the Service Form has been removed from 7.0.2 release due to security reasons. Instead, "DEBUG" in the ITDI log4j.properties file is to be used to enable extra debug logging.
|
|
N/A |
N/A |
Reset password for a user using the adapter/application has been restricted using Graph API.It is due to a recent security hole fix by Microsoft. https://support.microsoft.com/en-us/kb/3004133. This needs to be fixed via the solution provided in the link via Azure AD Module for Windows PowerShell (MSOL) cmdlets.
|
|
N/A |
N/A |
Only the license and service plans that are enabled for provisioning and are applicable at the user level, are available for provisioning using the adapter. Company wide licenses are not supported.
|
See the IBM Security Identity Adapter Installation and Configuration Guide for detailed instructions.
Corrections to Installation Guide
Corrections to Installation Guide
The following corrections to the Installation Guide apply to this release:
1. Add following content under Planning à Prerequisites à Table 1. Prerequisites to install the adapter.
|
Prerequisite |
Description |
|
SSL Configuration |
It is to be ensured that the MSIT Machine Auth CA2, login.windows.net and graph.windows.net certificates are in place. |
2. Add following Paragraph at the end under Installing à verifying that Adapter is working correctly:
Configuration Notes
The following configuration notes apply to this release:
The IBM Security Identity Manager adapters can be customized and/or extended. The type and method of this customization may vary from adapter to adapter.
Refer to the ‘IBM Security Identity Adapter Development and Customization Guide’
Support for Customized Adapters
The integration to the IBM Security Identity Manager server "the adapter framework" is supported. However, IBM does not support the customizations, scripts, or other modifications. If you experience a problem with a customized adapter, IBM Support may require the problem to be demonstrated on the GA version of the adapter before a case is opened.
Installation Platform
The IBM Identity and Security Adapter for Microsoft Office 365 was built and tested on the following product versions.
Adapter Installation Platform:
Due to continuous Java security updates that may be applied to your ISIM servers, the following SDI releases are the officially supported versions:
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:
Azure AD supported HTTP Client component:
· Apache HTTP Component Client
Ø Path to jar files in the package
httpcomponents-client-4.2.5-bin\httpcomponents-client-4.2.5\lib\commons-logging-1.1.1.jar
httpcomponents-client-4.2.5-bin\httpcomponents-client-4.2.5\lib\httpclient-4.2.5.jar
httpcomponents-client-4.2.5-bin\httpcomponents-client-4.2.5\lib\httpcore-4.2.4.jar
IBM Security Identity Manager:
Identity Governance and Intelligence (IGI):
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.