<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Multiple AD's connection to Cyberark in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-ad-s-connection-to-cyberark/m-p/1386352#M4687</link>
    <description>&lt;P&gt;We have multiple Active Directories (ADs) across different sites (Site A, Site B, Site C), and we are able to onboard users created in these sites into CyberArk with the help of our Main AD. However, we currently have only one AD (Main AD) integrated with CyberArk Cloud.&lt;/P&gt;&lt;P&gt;Apart from the ports required for CPM and PSM operations, do we need to open any additional ports if we are adding a new site? I would like to understand how CyberArk communicates between the sites.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS: There is no trust relationship between the ADs in different sites.&lt;/P&gt;</description>
    <pubDate>Wed, 14 May 2025 12:02:15 GMT</pubDate>
    <dc:creator>SupriyaDev</dc:creator>
    <dc:date>2025-05-14T12:02:15Z</dc:date>
    <item>
      <title>Multiple AD's connection to Cyberark</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-ad-s-connection-to-cyberark/m-p/1386352#M4687</link>
      <description>&lt;P&gt;We have multiple Active Directories (ADs) across different sites (Site A, Site B, Site C), and we are able to onboard users created in these sites into CyberArk with the help of our Main AD. However, we currently have only one AD (Main AD) integrated with CyberArk Cloud.&lt;/P&gt;&lt;P&gt;Apart from the ports required for CPM and PSM operations, do we need to open any additional ports if we are adding a new site? I would like to understand how CyberArk communicates between the sites.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PS: There is no trust relationship between the ADs in different sites.&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 12:02:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-ad-s-connection-to-cyberark/m-p/1386352#M4687</guid>
      <dc:creator>SupriyaDev</dc:creator>
      <dc:date>2025-05-14T12:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple AD's connection to Cyberark</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-ad-s-connection-to-cyberark/m-p/1386353#M4688</link>
      <description>&lt;P&gt;I believe you are asking about integrating Active Directory to allow users to login to Privilege Cloud with their AD accounts, and use AD groups for permissions within CyberArk, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the SaaS world, Active Directory integration is done by deploying the Identity Connector to a domain-joined machine. This is a lightweight agent that communicates to the CyberArk SaaS service using outbound https connection. It then acts as the proxy between the on-premises Active Directory and the SaaS service. See &lt;A alt="https://docs.cyberark.com/identity/latest/en/content/coreservices/connector/add-ad.htm?tocpath=Set%20up%20CyberArk%20Identity%7CAdd%20Users%7CAdd%20users%20from%20an%20external%20directory%20service%7C_____1" href="https://docs.cyberark.com/identity/latest/en/content/coreservices/connector/add-ad.htm?tocpath=Set%20up%20CyberArk%20Identity%7CAdd%20Users%7CAdd%20users%20from%20an%20external%20directory%20service%7C_____1" target="_blank"&gt;Add Active Directory as a directory service | CyberArk Docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For redundancy and performance you might install multiple Identity Connectors for each Active Directory domain, at least two connectors would be recommended. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So each Identity Connector requires only access to the Domain as provided by being installed on a server joined to that domain, and outbound connectivity to the CyberArk Identity SaaS service endpoint on https (port 443). The outbound https connection can be proxied, but SSL inspection must not be present.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no difficulty adding multiple Active Directories simply by installing Identity Connectors into each Active Directory environment. There is no need for the domains to communicate with each other.&lt;/P&gt;</description>
      <pubDate>Wed, 14 May 2025 14:19:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-ad-s-connection-to-cyberark/m-p/1386353#M4688</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-05-14T14:19:38Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple AD's connection to Cyberark</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-ad-s-connection-to-cyberark/m-p/1386354#M4689</link>
      <description>&lt;P&gt;Hello @Supriya Devaraj​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you received an answer to your question? If so, we kindly encourage you to share it with us.&lt;/P&gt;&lt;P&gt;Your insights could be valuable to other community members in the future.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you, Isar.&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 07:23:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/multiple-ad-s-connection-to-cyberark/m-p/1386354#M4689</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-22T07:23:09Z</dc:date>
    </item>
  </channel>
</rss>

