<?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 Re: How to switch cyberark identity connector? in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/how-to-switch-cyberark-identity-connector/m-p/1421864#M7709</link>
    <description>&lt;P&gt;Yes, it is feasible to switch to the other two connectors. CyberArk Identity Connectors are designed to support&amp;nbsp;automatic failover and load balancing—but this is&amp;nbsp;managed by the CyberArk tenant, not by customer-side infrastructure&amp;nbsp;&lt;/P&gt;&lt;P&gt;Automatic Failover: If a connector becomes unavailable, the CyberArk tenant will detect this and route traffic to another available connector.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Load Balancing: The tenant automatically selects the connector with the lowest latency. You do not need to configure a cluster or external load balancer for this to work&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;So, even though you mentioned that load balancing is not supported, the CyberArk tenant&amp;nbsp;does perform internal load balancing and failover&amp;nbsp;among connectors that are properly configured and online.&lt;/P&gt;</description>
    <pubDate>Thu, 21 Aug 2025 14:29:37 GMT</pubDate>
    <dc:creator>RobertS_Cyberark</dc:creator>
    <dc:date>2025-08-21T14:29:37Z</dc:date>
    <item>
      <title>How to switch cyberark identity connector?</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/how-to-switch-cyberark-identity-connector/m-p/1421863#M7708</link>
      <description>&lt;P&gt;We have a total of four CyberArk Identity Connectors that support integration between LDAPS and CyberArk Privilege Cloud. Currently, only two of these connectors are designated as primary, and all traffic is routed through them. We would like to understand if it's feasible to switch to the other two connectors, considering that load balancing is not supported. Additionally, how can we determine which Identity Connectors are actively handling LDAPS integration and which ones are not?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Jun 2025 14:30:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/how-to-switch-cyberark-identity-connector/m-p/1421863#M7708</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-06-16T14:30:15Z</dc:date>
    </item>
    <item>
      <title>Re: How to switch cyberark identity connector?</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/how-to-switch-cyberark-identity-connector/m-p/1421864#M7709</link>
      <description>&lt;P&gt;Yes, it is feasible to switch to the other two connectors. CyberArk Identity Connectors are designed to support&amp;nbsp;automatic failover and load balancing—but this is&amp;nbsp;managed by the CyberArk tenant, not by customer-side infrastructure&amp;nbsp;&lt;/P&gt;&lt;P&gt;Automatic Failover: If a connector becomes unavailable, the CyberArk tenant will detect this and route traffic to another available connector.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Load Balancing: The tenant automatically selects the connector with the lowest latency. You do not need to configure a cluster or external load balancer for this to work&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;So, even though you mentioned that load balancing is not supported, the CyberArk tenant&amp;nbsp;does perform internal load balancing and failover&amp;nbsp;among connectors that are properly configured and online.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 14:29:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/how-to-switch-cyberark-identity-connector/m-p/1421864#M7709</guid>
      <dc:creator>RobertS_Cyberark</dc:creator>
      <dc:date>2025-08-21T14:29:37Z</dc:date>
    </item>
  </channel>
</rss>

