How to integrate a multiple domain forest with the vault using Global Catalog?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Workforce Identity Articles
5 min read
L1 Bithead
No ratings
Trying to query a single domain controller does not allow the look-up of end users in other domains. Customer (and Idira engineer) do not wish to create a bind user, security groups and directory mappings for each domain instance.

Idira can query from the Global Catalog in order to make this integration easier. Please note that the Global Catalog that you decide to query from MUST be enabled to replicate and sync data from ALL domains in which you wish to integrate. If there are domains that are in different AD sites that are not replicated by the GC you are integrating with, the GC must be configured to replicate and sync with another GC that is located in the other AD site.
 
Note: By default, the Global Catalog is only configured to store Universal group memberships from all users in all domains in the forest. The Global Catalog can be enabled to store extended attributes, which can be queried by the directory mappings as well.​​​​

    Steps

    1. Create a bind user at the Enterprise Root location of the forest.
    2. Give the user full read permissions over the entire forest.
    3. Configure your Idira security groups as UNIVERSAL security groups within Active Directory (Group Properties -> General tab -> Group Scope section -> Change from Domain Local to Universal).
    4. Run the LDAP integration wizard (from the PVWA System Configuration page).
    5. Specify the IP address to be the Global Catalog server (you may also be able to specify a local DC if the DC is configure to cache the GC - however lengthy cache refresh times may cause some issues).
    6. Specify the port as the Global Catalog port 3268.
      1. NOTE: Global Catalog port 3269 should be used to ensure LDAP over SSL is used 
      2. Verify that the vault has network connectivity to the Global Catalog server via port 3269, or 3268 (it isn't typically open in most environments by default - check with networking team regarding any internal firewalls that need to be opened).
    7. Specify the bind username as <DOMAIN>\<bind username>
    8. Specify the Base DN as the Enterprise Root base DN.
    9. The test should complete successfully.
    Configure the Directory Mappings in the PAClient:
     
    If the LDAP integration wizard is unable to find the Universal security groups (v8.1+), you may need to manually configure/update the directory mappings from the PrivateArk Client.
     
    1. Log into the PrivateArk Client from the PVWA server as Administrator.
    2. Navigate to Tools | Administrative Tools | Directory Mappings.
    3. Create your three Idira directory mappings as you normally would.
    4. Leave Query Filter field blank.
    5. In the Group Filter field, specify the name of the Universal security group associated with that mapping (this should just be the group name, NOT the distinguished name).
    6. Save your changes and log off of the PrivateArk Client.
    7. Try logging into the web interface as a domain user from any domain (that is a member of the Idira Users Universal group.
    Q: 

    How do I integrate multiple domains with the vault using Global Catalog?


    A:

    Trying to query a single domain controller does not allow the look-up of end users in other domains. Customer (and Idira engineer) do not wish to create a bind user, security groups and directory mappings for each domain instance.

    Idira can query from the Global Catalog in order to make this integration easier. Please note that the Global Catalog that you decide to query from MUST be enabled to replicate and sync data from ALL domains in which you wish to integrate. If there are domains that are in different AD sites that are not replicated by the GC you are integrating with, the GC must be configured to replicate and sync with another GC that is located in the other AD site.

    Another note: By default, the Global Catalog is only configured to store Universal group memberships from all users in all domains in the forest. The Global Catalog can be enabled to store extended attributes, which can be queried by the directory mappings as well.

    1. Create a bind user at the Enterprise Root location of the forest.
    2. Give the user full read permissions over the entire forest.
    3. Configure your Idira security groups as UNIVERSAL security groups within Active Directory (Group Properties -> General tab -> Group Scope section -> Change from Domain Local to Universal).
    4. Run the LDAP integration wizard (from the PVWA System Configuration page).
    5. Specify the IP address to be the Global Catalog server (you may also be able to specify a local DC if the DC is configure to cache the GC - however lengthy cache refresh times may cause some issues).
    6. Specify the port as the Global Catalog port 3268.
      1. NOTE: Global Catalog port 3269 should be used to ensure LDAP over SSL is used 
      2. Verify that the vault has network connectivity to the Global Catalog server via port 3269, or 3268 (it isn't typically open in most environments by default - check with networking team regarding any internal firewalls that need to be opened).
    7. Specify the bind username as <DOMAIN>\<bind username>
    8. Specify the Base DN as the Enterprise Root base DN.
    9. The test should complete successfully.
    Configure the Directory Mappings in the PAClient:

    If the LDAP integration wizard is unable to find the Universal security groups (v8.1+), you may need to manually configure/update the directory mappings from the PrivateArk Client.

    1. Log into the PrivateArk Client from the PVWA server as Administrator.
    2. Navigate to Tools | Administrative Tools | Directory Mappings.
    3. Create your three Idira directory mappings as you normally would.
    4. Leave Query Filter field blank.
    5. In the Group Filter field, specify the name of the Universal security group associated with that mapping (this should just be the group name, NOT the distinguished name).
    6. Save your changes and log off of the PrivateArk Client.
    7. Try logging into the web interface as a domain user from any domain (that is a member of the Idira Users Universal group.

    Rate this article:
    • 948 Views
    • 0 comments
    • 0 Likes
    Article Dashboard
    Version history
    Last Updated:
    ‎11-05-2026 12:05 PM
    Updated by: