Setting Up a Microsoft Active Directory (AD) Bridge
The Microsoft Active Directory (AD) Bridge provides a link between your AD enterprise directory structure and IAM.
Understand the Microsoft Active Directory (AD) Bridge
IAM can synchronize with this directory structure so that any new, updated, or deleted user or group records are transferred into IAM. Each minute, the AD Bridge polls AD for any changes to these records and brings these changes into IAM. So, if a user is deleted in AD, then this change will be propagated into IAM. Because of this synchronization, the state of each record is synchronized between AD and Identity Domains.
After users are synchronized from AD to IAM, if you activate or deactivate a user, modify the user's attribute values, or change the group memberships for the user in IAM, then these changes are propagated to AD through the AD Bridge.
The AD organizational units (OUs) contain the users and groups that are imported into IAM.
You can configure IAM to synchronize with one or multiple AD domains by installing an AD Bridge for each domain.
You must install the AD Bridge on the machine that’s attached to the Microsoft Active Directory domain for auto discovery. You don’t have to install the bridge on the domain controller.
In the diagram above, Clarence Saladna (CSALADNA) is a user who's been synchronized from AD to IAM through the AD Bridge. In IAM, an administrator deactivates Clarence's account because he's on vacation. Also, because Clarence received a promotion, he has a new job title of Director and belongs to different groups that are associated with his new role, including the Executive and Management groups. The AD Bridge can be used to propagate these changes to AD.
Both the AD Bridges and your AD enterprise directory structure are in your Microsoft Windows environment (for example, Microsoft Windows 2003). Because IAM is an Oracle Cloud service, it's in an Oracle environment.

If an AD user attribute is multi-valued, then the AD Bridge will transfer only the first value of the attribute into IAM.
Certified Components
The following table lists the certified versions for IAM, AD, your operating system, and the Microsoft .NET software framework (which is required for the AD Bridge to run).
IAM | AD | 64–Bit | Operating System | .NET Framework |
---|---|---|---|---|
20.1.3 |
Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2012 Microsoft Windows Server 2012 R2 Microsoft Windows Server 2016 Microsoft Windows Server 2019 |
Yes |
Windows 10 v1607 or later Windows Server 2016 or later |
Version 4.6+ |
Statuses
-
Partially Configured: The AD Bridge is installed, but it's not configured to communicate with either the AD domain or IAM.
-
Configured: The AD Bridge is installed and configured, and available to synchronize with the AD domain.
-
Active: The AD Bridge is installed and configured, and available to synchronize with AD to retrieve user accounts and groups.
-
Inactive: The AD Bridge is installed and configured, but it's not available to synchronize with AD. For performance reasons, this is done.
-
Unreachable: The AD Bridge is installed and configured. However, one of the following conditions has occurred:
-
The back-end service used to establish communication between IAM and AD is stopped.
-
The IAM administrator uninstalled the client associated with the AD Bridge, but the bridge couldn't be removed from the Directory Integrations page of the IAM Console because the client can't connect to the Identity Domains server. IAM can't use the bridge to communicate with AD. See Remove a Microsoft Active Directory (AD) Bridge.
-
The administrator regenerated the Client Secret for the AD Bridge, and then uninstalled the client for the bridge.
-
Hardware Requirements
The minimum hardware requirements are:
- 1 GB of RAM
- 1 GB of disk space
- A quad-core CPU
Why Use the Microsoft Active Directory (AD) Bridge?
Most customers have AD as their central directory service. These customers also use AD as their network directory. This directory is where all of their workstations are connected to and from where they manage their users.
In addition to AD, customers use an enterprise LDAP to centralize all of their user identities. So, a customer uses AD to manage their employees, but in the centralized LDAP, the customer manages their partners, consumers, and any other users with which the customer has relationships.
For these reasons, it's imperative that IAM can integrate with both AD and an enterprise LDAP (for example, Oracle Internet Directory).
- AD Bridge: This bridge provides a link between your AD enterprise directory structure and IAM. IAM can synchronize with this directory structure so that any new, updated, or deleted user or group records are transferred into IAM. Each minute, the bridge polls AD for any changes to these records and brings these changes into IAM. So, if a user is deleted in AD, then this change will be propagated into IAM. As a result, the state of each record is synchronized between AD and IAM. After the user is synchronized from AD to IAM, if you activate or deactivate a user, modify the user's attribute values, or change the group memberships for the user in Identity Domains, then these changes are propagated to AD through the AD Bridge.
- Provisioning Bridge: This bridge provides a link between your enterprise LDAP (such as Oracle Internet Directory) and IAM. Through synchronization, account data that’s created and updated directly on the LDAP is pulled into IAM and stored for the corresponding IAM users and groups. As a result, any changes to these records will be transferred into IAM. Because of this, the state of each record is synchronized between the LDAP and IAM. See Managing Provisioning Bridges.
About Multiple AD Bridges for High Availability and Load Balancing
If you only have one Microsoft Active Directory (AD) Bridge component in one Windows Service connecting to your Active Directory domain, it can be a single point of failure in the architecture.
To avoid this, IAM supports the installation of multiple AD Bridge instances mapping to the same Active Directory domain.
The maximum number of AD Bridges that an administrator can install per domain must not exceed five (5). In addition, the maximum number of domains that an administrator can configure per tenant must not exceed 10. To configure these limits, raise an SR with Oracle Support.
With a AD Bridge High Availability (HA) deployment of at least two AD Bridges per domain, delegated authentication and data synchronization loads can be shared among all the AD Bridges. The allocation of requests to a AD Bridge is completely random, depending on the availability of that particular AD Bridge. One delegated authentication request will be picked up by one AD Bridge. An AD Bridge can pick delegated authentication and full or incremental synchronization as well. Both AD Bridges have the capability to perform data synchronization and delegated authentication simultaneously. However, only one AD Bridge can perform data synchronization of a domain at a time.
Enable HA for an Existing Deployment
Prerequisites
- Ensure that you have upgraded the existing AD Bridge to version 20.1.3 and greater for every domain that you have configured.
- AD Bridge HA must be enabled for you. Once all AD Bridges in all domains have been upgraded to version 20.1.3 or greater, enter an SR with Oracle Support to enable HA. Once HA is enabled, it is enabled for all configured domains.
Limitations
- Only one AD Bridge can be configured in one Windows machine. To configure multiple AD Bridges you have to use multiple Windows machines in the same domain. Note that without AD Bridge HA enabled by Oracle Support, installation of second AD Bridge for the domain will fail.
- Maximum of 5 AD Bridges per domain can be configured by an Administrator for HA and load sharing.
- AD Bridge HA won’t work if any one of the AD Bridges installed for a domain is version 19.3.3 and below. To check the version of an AD bridge, open the AD Bridge user interface and note the version in the bottom right corner of the window.
If additional bridges won’t install for a domain, make sure that all prerequisites are met and that none of the constraints apply to your environment.
Enable HA for a New Deployment
Enable HA
AD Bridge High Availability must be enabled for you. Enter an SR with Oracle Support to enable the feature.
Limitations
- AD Bridge HA will not work if any one of the AD Bridges installed for a domain is version 19.3.3 and below.
- Only one AD Bridge can be configured in one Windows machine. To configure multiple AD Bridges you have to use multiple Windows machines in the same domain. Note that without AD Bridge HA enabled by Oracle Support, installation of second AD Bridge for the domain will fail.
- Maximum of 5 AD Bridges per domain can be configured by an Administrator for HA and load sharing.
If additional bridges won’t install for a domain, make sure that all prerequisites are met and that none of the constraints apply to your environment.
Checking a Bridge Data Synchronization Status
Test Active Directory Connectivity
- Connectivity between AD Bridge and LDAP server of Active Directory
- Connectivity between AD Bridge and IAM
- Open ADBridgeUI.exe. It’s in the ADBridge installation folder. The default path is C:\Program Files\Oracle\IDBridge.
- Click the Test Connectivity button.
AD Bridge Connectivity Notifications
Learn about notifications that IAM sends to the tenant admin when connectivity between AD Bridge and the IAM server is broken and also when it is restored.
Notifications sent when connectivity of AD Bridge with IAM server is broken
Oracle sends notifications to the tenant admin when connectivity between AD Bridge and the IAM server is broken. Connectivity could be broken because of multiple reasons, for example if the AD Bridge is stopped or if the IAM is stopped on the Windows machine.
The notifications will have the email subject: Connectivity to AD bridge <windows machine name> is unreachable.
Notifications sent when connectivity of AD Bridge with IAM server is restored
Similarly, when connectivity is restored, an email will be sent from Oracle to the tenant administrator.
The notifications will have the email subject: Connectivity to AD bridge <windows machine name> is restored.
Use REST API to Configure Email Notifications
Using the REST API, Administrators can configure who should receive email notifications when connectivity is broken and restored.
The Administrator can provide comma separated list of emails IDs to which to send the notifications using PATCH /admin/v1/Settings/Settings
.
{
"schemas":[
"urn:ietf:params:scim:api:messages:2.0:PatchOp"
],
"Operations":[
{
"op": "replace",
"path": "contactEmails",
"value": [
"admin@oracle.com",
"<emailid>@gmail.com"
]
}
]
}
Set Permissions for Your Microsoft Active Directory (AD) Account
Use your Microsoft Active Directory (AD) domain administrator account to create an AD Bridge. Before creating this bridge, you must set permissions for your account. You must set these permissions so that you can install the bridge and configure delegated authentication for it.
With delegated authentication, identity domain administrators and security administrators don’t have to synchronize user passwords between AD and IAM. Users can use their AD passwords to sign in to IAM to access resources and applications protected by IAM.
Setting Permissions to Synchronize Users, Groups, and Group Membership
Setting Permissions to Propagate Changes to Microsoft Active Directory
Setting Permissions for Delegated Authentication
Creating a Microsoft Active Directory (AD) Bridge
To create a Microsoft Active Directory (AD) Bridge that provides a link between your AD enterprise directory structure and IAM, you must be assigned to either the identity domain administrator role or the security administrator role. You must also have administrative rights to access the AD domain that you want to monitor by using the bridge.
Part of creating the AD Bridge is providing administrative credentials for both AD and IAM. The bridge requires these credentials to communicate with AD and IAM as an administrator.
-
Generic Read for the users and groups in the AD domain that you want to import into IAM
-
Generic Read for all organizational units (OUs) in the domain
-
Generic Read for the cn=Configuration container in the domain
-
The List Children and Read properties for the cn=Deleted Objects container with inheritance
If this account is also used to configure delegated authentication for the AD Bridge, then the account should have the following permissions:
-
Change Password
-
Reset Password
-
Read pwdLastSet
-
Write pwdLastSet
-
Read lockoutTime
-
Write lockoutTime
You can access the Managing security settings infographic to see how to create an AD Bridge.
Configuring a Microsoft Active Directory (AD) Bridge
After creating a Microsoft Active Directory (AD) Bridge, you configure it by:
-
Selecting the AD organizational units (OUs) and groups with which you want IAM to synchronize using the AD Bridge. The OUs contain the users that you want to import into IAM. By synchronizing with AD, the bridge can transfer new, updated, or deleted user or group records into IAM.
- Specifying whether, after a user or group is synchronized from AD to Identity Domains, if you activate or deactivate a user, modify the user's attribute values, or change the group memberships for the user in IAM, these changes will be propagated to AD.
-
Scheduling how often you want IAM to use the AD Bridge to import users and groups from AD.
-
Defining custom attribute mappings between AD and IAM.
-
Specifying whether users can use their IAM or AD passwords, or their federated accounts, to authenticate into IAM to access resources that are protected by IAM, such as the My Profile Console, the IAM Console, or any apps assigned to the users.
You can access the Managing Security Settings infographic to see how to configure an AD Bridge.
Defining Attribute Mappings for a Microsoft Active Directory (AD) Bridge
By default, when you create a Microsoft Active Directory (AD) Bridge, attribute mappings are defined between AD and IAM. Attribute mappings enable the AD Bridge to pass values associated with user accounts between AD and IAM.
You can map attributes in two different ways: inbound and outbound. Inbound mappings allow you to map attributes from AD to IAM. Outbound mappings allow you to map any changes in IAM attributes to AD attributes.
For example, when you run the AD Bridge, the bridge can use the givenName -
First Name
mapping to transfer the first name of the user account from
the First name field on the General
tab of the Properties window of AD to the First
Name field on the Details tab of the
Users page of IAM. Similarly, you can
perform an outbound mapping so that when you make any change to the first name of
the user account in IAM, this change is reflected in AD.
In addition to the predefined attribute mappings, you can define custom attribute mappings between AD and IAM.
Understanding Full and Incremental Sync
You can synchronize users and groups from selected organizational units (OUs) in Microsoft Active Directory (AD) into IAM. You can perform either an incremental sync or a full sync. Learn about syncing new OUs and read some example use cases.
Syncing New Organizational Units
Before 20.1.3, OU sync was triggered by the Bridge every minute so that newly added OUs in Active Directory were automatically available in IAM. Starting with the 20.1.3 release, when you add a new organizational unit (OU) in Active Directory, you must perform an incremental or full sync to see the newly created OU in IAM. Oracle recommends that you to run an incremental sync when adding new OUs.
Use Case: Unlink Users from Microsoft Active Directory (AD)
When you perform a full sync on users from organizational units (OUs), all users in the selected OUs are synchronized in IAM. The next time you apply a filter to synchronize a specific OU, you perform an incremental sync and the users in that OU are resynchronized in IAM.
The synchronized users who were not part of the filter will be unlinked from Microsoft Active Directory (AD). The unlinked users can no longer authenticate using delegated authentication because their link to AD is removed and their authentication falls back to IAM. Any new updates to these users won't be synced to IAM. You can use IAM to reset the passwords for these users. When you request a password change for the users, IAM sends a Password Reset notification to them so that they can provide their new passwords.
If you remove the filter and synchronize these users again using full sync, then all of the users who were unlinked earlier will now be linked, and their authentication will fall back to AD.
Consider Human Resource and Marketing OUs with five users each. You are using full sync to sync them from AD to IAM. All of the users are synced in IAM.
If you want the Marketing users alone in IAM, then you can perform an incremental sync along with a filter to resync the Marketing users into IAM. All of the users who are part of the Human Resource OU are unlinked because they're not part of the filter that's used to resync users. The number of unlinked users appears in the UI.
Item | Description |
---|---|
![]() |
A full sync from Microsoft Active Directory will unlink the users who are not synced in the identity domain either due to change in OU selection or increase/decrease in the scope of the filter. |
Use Case: Delete Users and Groups from Microsoft Active Directory (AD)
Microsoft Active Directory (AD) is an authoritative source. Users that are deleted from AD are unlinked and deactivated in IAM. You can then remove these users from IAM.
When groups are deleted from AD, upon a full or incremental sync, these groups are also removed from IAM.
Use Case: Reattach an Unlinked User in IAM
Consider you want to create previously unlinked users in Microsoft Active Directory (AD) with the same usernames. When you next perform a full or an incremental sync, these users in AD are reattached to the associated users in IAM.
The reattached user’s authentication will be delegated to AD if delegated authentication is activated in IAM. For example, a user is synced from multiple AD domains into IAM. All of these domains are authoritative because AD is an authoritative source. If you delete a user from one of the domains, then the user is unlinked in IAM. If you resync the user to a different AD domain, then this domain now becomes authoritative for the user.
Activate and Deactivate Microsoft Active Directory (AD) Bridges
Use IAM to activate and deactivate Microsoft Active Directory (AD) Bridges:
-
Deactivate: Disable the link between your AD enterprise directory structure and IAM.
-
Activate: Enable the link between IAM and AD.
Modify a Microsoft Active Directory (AD) Bridge
You can change the following items for a Microsoft Active Directory (AD) Bridge:
- The AD users and groups that you want IAM to import using the AD Bridge.
- Whether, after a user or group is synchronized from AD to IAM, if you activate or deactivate a user, modify the user's attribute values, or change the group memberships for the user in IAM, these changes will be propagated to AD.
- How often you want IAM to use the AD Bridge to import users and groups from AD.
- The predefined and custom attribute mappings defined between AD and IAM.
- Whether users can use their AD or their IAM passwords, or their federated accounts, to sign in to IAM to access resources protected by IAM, such as the My Profile Console, IAM Console, and apps assigned to the users.
You can upgrade the client for the AD Bridge. By doing this, you can install the latest client without removing the existing client that's installed.
To upgrade the client, download it and follow the instructions in Create a Microsoft Active Directory (AD) Bridge. When you see the Specify Oracle Identity Cloud Service Credentials or the Specify Microsoft Active Directory Credentials dialog boxes, the client will use the credentials you provided in the previous installation. For this reason, the values are greyed out so they can't be edited.
Using the Console
You can run a Microsoft Active Directory (AD) Bridge to synchronize IAM with AD immediately.
As part of configuring an AD Bridge, you specified how often, in hours and minutes, you want IAM to use the bridge to import users and groups from AD. You're synchronizing IAM with your AD enterprise directory structure.
When the interval you specified elapses, IAM synchronizes with the directory structure so that any new, updated, or deleted user or group records are transferred into IAM. Because of this, the state of each record is synchronized between AD and IAM.
- Full import: The AD Bridge polls AD and retrieves data associated with all user and groups that you selected in the Select organizational units (OUs) for users and Select organizational units (OUs) for groups panes of the Configuration tab for the bridge. This data represents users and groups that were created, modified, or removed in AD. As a best practice, Oracle recommends that you perform a full import the first time you run the AD Bridge.
- Incremental import: Similar to a full import, but for this type of import, the AD Bridge polls AD and retrieves only user and group data that changed since you last used the AD Bridge to import users and groups into IAM.
By running the AD Bridge, you can propagate changes for IAM users in AD. After users are imported into IAM through the bridge, if you activate or deactivate a user, modify the user's attribute values, or change the group memberships for the user in IAM, then these changes will be reflected in AD.
You can also use the AD Bridge to view a synchronization log of the communication between IAM and AD.
If you can't remove the client for the AD Bridge or the bridge still appears in the Directory integrations page, then complete the following steps:
- Run the following CURL command to obtain the Client ID that you used to install the client for the AD Bridge:
curl -X GET \ <Identity_Cloud_Service_URL>/admin/v1/IdentityAgents \ -H 'Authorization: Bearer <access_token>
<Identity_Cloud_Service_URL>
is a placeholder for the IAM URL that you used to install the client for the bridge, and<access_token>
is a placeholder for the access token that contains the authorization credentials that are required to obtain the Client ID.See the IAM: First REST API Call tutorial to learn how to get this access token.
A list of AD Bridge clients that are installed for your identity domain appears.
- From this list, find the Client ID of the AD Bridge that you want to remove.
- Run the following CURL command to remove the client for the AD Bridge:
curl -X DELETE \ <Identity_Cloud_Service_URL>/admin/v1/IdentityAgents/<Client_ID> \ -H 'Authorization: Bearer <access_token>
<Client_ID>
represents the ID of the client for the AD Bridge that you want to remove.A
204 (No Content)
response appears, signifying that you removed the client for the bridge.
Transfer the Microsoft Active Directory (AD) Bridge
Maintaining the Microsoft Active Directory (AD) Bridge includes transferring the bridge to another machine and restarting the bridge.
Transferring the Microsoft Active Directory (AD) Bridge
After you have setup a Microsoft Active Directory (AD) Bridge, you can transfer that bridge to another machine.
If you can't remove the client for the AD Bridge or the bridge still appears in the Directory Integrations page, then follow the procedure in Removing a Microsoft Active Directory (AD) Bridge.
- From the original machine, access the Control Panel, and uninstall the client for the AD Bridge.
- On the other machine, install the client. See Create a Microsoft Active Directory (AD) Bridge.
- In the IAM Console, expand the Navigation Drawer, click Settings, and then click Directory Integrations.
- Verify that the AD Bridge appears in the other machine with an Active status. This bridge can now be used to synchronize with your AD enterprise directory structure.
Restarting the Microsoft Active Directory (AD) Bridge
Log Files
Understand how to manage the log files created by the Microsoft AD Bridge, and how to let Oracle access them on demand for support.
Creating and Managing Log Files for the Microsoft Active Directory (AD) Bridge
After you install and configure the Microsoft Active Directory (AD) Bridge, you may want to access the log files for troubleshooting purposes. You can locate these files in the %ProgramData%\Oracle\IDBridge\logs directory.
To modify the log level of the log files for the AD Bridge:
You must restart the AD Bridge for the change you made to the log level to take effect.
Allowing My Oracle Support to Access Client Log Files
When My Oracle Support are diagnosing Microsoft AD bridge issues, they might need access to the Microsoft AD Bridge client log files.
The default behavior is that My Oracle Support cannot access the client log files, which are on a machine at your premises. You have to add them to the support request. You can give your consent so that My Oracle Support can fetch the logs directly when they need to be analyzed to resolve an issue. This can reduce the time it takes for the support request to be resolved.
Learn about the scope of consent, what it covers, and how long it lasts:
- How long does consent last?
After you have given your consent, it remains effective until you remove your consent, or remove the AD Bridge domain.
- Do I need to give separate consent for every AD Bridge?
No. Your consent applies at AD domain level. If you have more than one bridge under the same AD domain, the consent applies to all of them.
- Do I need to provide consent for each AD domain?
If you have more than one AD domain, a separate consent is needed for each one.
- Can Oracle fetch any file from the windows machine where the Microsoft AD Bridge client is installed?
No. Only Microsoft AD Bridge log files are fetched.
- When is the log file fetched from the client machine?
Oracle only fetches logs files if they are needed so they can be analyzed as part of resolving a service request that you have raised. If you raise a service request and there is no need for the AD Bridge client log file to be examined, then it is not fetched.
- Where are the log files stored?
They are uploaded to tenant Oracle cloud storage.
- Do the log files stay in cloud storage indefinitely?
No. They will be removed from cloud storage after 24 hours, after Oracle has analyzed the logs. An automated purge job deletes all log files that are older than 24 hours.